Thanks Dante and Mary!
That was an amazing response despite what I know is likely quite a busy schedule due to end of year, start of year stresses.
I will start working my new project version in (wpf) to get exposure to (xaml) and dot-net 6.
Also, I guess its time to switch to (c#) from (vb) all be it I personally find (vb) the superior programming language.
Thanks again to Dante and the MS team for helping out at light-speed.
Richard R. Thomas (Rick USA)
Sent from Mail for Windows
From: Dante Gagne
Sent: Tuesday, January 4, 2022 1:57 PM
To: program-l@xxxxxxxxxxxxx; Merrie McGaw (SHE/HER)
Subject: [program-l] Re: VisualStudio DotNet6 Inaccessibility Issue
Slightly editing response from mailto:Merrie.McGaw@xxxxxxxxxxxxx on the .NET team:
The accessibility issues only applies to WinForms Designer for .NET projects. The workaround still works. And WPF designer works just fine for any version of .NET/.NET Framework. You can modify the project file to multi-target for both netfx48 and net64-windows. If net48 is listed first, the framework designer will work. So, the line in your proj file will look like:
<TargetFrameworks>net48;net6.0-windows</TargetFrameworks>
As for a fix, We're working on it for an upcoming servicing release and will keep you posted. Holidays and surprising security events have impacted us.
As for converting wpf or Win-Forms to maui to run on desktop machines and perhaps phones downline. Honestly, MAUI is going to be a XAML based authoring - which would be an entirely different design paradigm from WinForms. You have a tough choice to either make an easier move to WinForms on .NET 6 but have missing support in the designer window only (code editing is still fine). Then when you move to MAUI you'd have the migration challenge of moving to a XAML based layout paradigm. Alternatively you could migrate to WPF -> .NET 6 -> MAUI. Honestly there is no best answer here. My thought would be that since you want to have both desktop and phone support it might be best if you bite the bullet and learn XAML models now and migrate to WPF at the same time as migrating to .NET 6. WinForms is getting improvements and updates (especially supporting better accessibility) but WinForms is not the same design model as what your end goals would require. OliaG would be a great resource to talk
about the migration path she's seeing her customers use that are in similar situations.
From: program-l-bounce@xxxxxxxxxxxxx <program-l-bounce@xxxxxxxxxxxxx> On Behalf Of Rick USA
Sent: Tuesday, January 4, 2022 9:23 AM
To: program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: VisualStudio DotNet6 Inaccessibility Issue
Thanks Dante:
I had been waiting for several months, most all year, for maui but it was pushed back into next year.
Now I have to get moving and wanted to use the new enhanced Jason features, and others, of dot net 6.
Thanks for checking with the teams and supporting the folks on this list who rely on accessibility to get the job done.
Richard R. Thomas (Rick USA)
Sent from https://go.microsoft.com/fwlink/?LinkId=550986 for Windows
From: mailto:dmarc-noreply@xxxxxxxxxxxxx
Sen t: Tuesday, January 4, 2022 12:03 PM
To: mailto:program-l@xxxxxxxxxxxxx
Subject: [program-l] Re: VisualStudio DotNet6 Inaccessibility Issue
I'm reaching out to the .NET team and I'll hopefully have some answers for you today.
--Dante
From: mailto:program-l-bounce@xxxxxxxxxxxxx <mailto:program-l-bounce@xxxxxxxxxxxxx> On Behalf Of Rick USA
Sent: Tuesday, January 4, 2022 7:24 AM
To: Program-L@Freelists. Org <mailto:program-l@xxxxxxxxxxxxx>
Subject: [program-l] VisualStudio DotNet6 Inaccessibility Issue
; I am working on updating large and complicated vb dot net (Dot Net 4.7) Desk-Top Win-Forms projects and want to use some tools from dot net 6.
Dot Net 6 designers are inaccessible in visual studio 2022.
Any word on when MS will fix this issue?
Also, Would wpf or Win-Forms be a better choice for easier conversion to maui to run on desktop machines and perhaps phones downline?
Any other suggestions as to project types toward these purposes?
Again, thanks for any insights and suggestions:
Richard R. Thomas (Rick USA)e.
< p class=MsoNormal>Sent from https://go.microsoft.com/fw%20link/?LinkId=550986 for Windows
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** mailto:program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** mailto:program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** mailto:program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** mailto:program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe]
** If this link doesn't work then send a message to:
** program-l-request@xxxxxxxxxxxxx
** and in the Subject line type
** unsubscribe
** For other list commands such as vacation mode, click on the
** immediately-following link:-
** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq]
** or send a message, to
** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
** To leave the list, click on the immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=unsubscribe] ** If this link doesn't work then send a message to: ** program-l-request@xxxxxxxxxxxxx ** and in the Subject line type ** unsubscribe ** For other list commands such as vacation mode, click on the ** immediately-following link:- ** [mailto:program-l-request@xxxxxxxxxxxxx?subject=faq] ** or send a message, to ** program-l-request@xxxxxxxxxxxxx with the Subject:- faq
