[.NET5] Validation of experience for Visual Basic

[kvenkatrajan]

Github mirror of AB#1302808

• Cannot change the Startup Form in a .NET 5 WinForms Application Framework VB App. #6787 (done. *)
• StartupObject property is not erased after enabling Application Framework property #6608 (done. This is in .net core. Won't fix)
• App.config is not created when Settings are modified #7772
• Setting do not work on NEW VB .Net 5 Winforms application #7448 (done. *)
• Duplicate root namespace in settings file with sdk-style project #7102 (done. This is in .net core. Won't fix)
• Updating the Default Settings file in a WinForms .NET 5 Visual Basic app fails. #6784
• Unsupported MyApplication Properties removed from Application.Designer.VB #6659 (done. Low priority. Won't fix)
• AB#1517428 (fixed)
• In VB .NET Core projects, "Disable all warnings" of "Compile" tab doesn't work for some warnings #3102
• Buggy namespace selection via keyboard-only #3071
• Removing Microsoft.VisualBasic import in .NETStandard Lib throws poor Error Message #2706 (done. *)
• VB: .NET Standard class library project should honour defaults specified in Options window. #3040 (Broken in old project system)
• View Windows Setting button in VB .NET Core app page adds an extra backslash to the project file #2344
• An error occurred while saving values to the app.config file #8207

* No change needed in the old project system. It works well for .net frameworks

[ocallesp]

For the list of issues, we should only fix the ones that are in the new Project System.

cc: @kvenkatrajan

[drewnoakes]

For the list of issues, we should only fix the ones that are in the new Project System

@ocallesp could you explain what you mean by this?

[ocallesp]

After a meeting with @melytc and @kvenkatrajan we prioritized to fix only bugs in the old project system for the old property pages.

I confirmed with @KlausLoeffelmann that there are no bugs in the property pages for .net framework vb

[KlausLoeffelmann]

No, that's not correct.
There are NO bugs to my knowledge in .NET Framework, only in .NET.

[Update]: Now it's correct! 😄

[kvenkatrajan]

After a meeting with @melytc and @kvenkatrajan we prioritized to fix only bugs in the old project system for the old property pages.

I confirmed with @KlausLoeffelmann that there are bugs in the property pages for .net framework vb

Just to confirm the expectations Osvaldo-
We would want to fix any issues identified in the legacy property pages on the legacy project system & similarly ensure that these issues cease to exist with new property pages built on top of the new project system

[KlausLoeffelmann]

So, I think the confusion here is, that the WinForms Design of the "old" Project System AppDesigner is intuitively connected to Framework Apps, while the WPF-style Pages are connected to .NET.

This is NOT true for VB!

Even for .NET, the old pages are based on the WinForms Project System AppDesigner. And that scenario (only .NET!) is utterly broken. Framework (with old WinForms AppDesigner) works just fine!

[kvenkatrajan]

Yes that is correct. We are aware of that and the work to port it to the new WPF pages is being tracked and worked here in parallel with this validation effort-
#8057

[ocallesp]

It seems that we can close #6608 and #6787 since they are working correctly in .Net Framework for VB. (No issues in the Old Project System Old Property Pages WinForms)

[ocallesp]

From this list only #3040 and AB#1517428 should be fixed.

AB#1517428 has higher priority than #3040

cc: @kvenkatrajan @melytc

[ocallesp]

AB#1517428 fixed with this pr.

[ocallesp]

The only pending work is #3040