Osvaldo Calles

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)

From this list only #3040 and [AB#1517428](https://devdiv.visualstudio.com/0bdbc590-a062-4c3f-b0f6-9383f67865ee/_workitems/edit/1517428) should be fixed. [AB#1517428](https://devdiv.visualstudio.com/0bdbc590-a062-4c3f-b0f6-9383f67865ee/_workitems/edit/1517428) has higher priority than #3040 cc: @kvenkatrajan @melytc

[AB#1517428](https://devdiv.visualstudio.com/0bdbc590-a062-4c3f-b0f6-9383f67865ee/_workitems/edit/1517428) fixed with this [pr](https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_git/VS/pullrequest/400783).

The only pending work is https://github.com/dotnet/project-system/issues/3040

After doing some investigation, this issue is in the new ProjectSystem https://github.com/dotnet/project-system/blob/main/src/Microsoft.VisualStudio.Editors/PropPages/ApplicationPropPageVBWinForms.vb#L1557 This is incorrectly handling the case when unchecked. cc: @kvenkatrajan

@KlausLoeffelmann It seems that StartupObject should be stored in Application.myapp and not in the project file based on the last comment in https://github.com/dotnet/project-system/issues/6787 What should be the expected behavior when...

This is working correctly in .net framework property pages for VB

Assigning this to me since this can help ramp-up in with https://github.com/dotnet/sdk/issues/1458

Maybe we should publish packages to NuGet.org for this [specific versions of VS](https://docs.microsoft.com/en-us/visualstudio/install/visual-studio-build-numbers-and-release-dates?view=vs-2022).

Does not repro. Based on the stack provided, this is in the Cps layer.  But there are [other issues](https://github.com/dotnet/roslyn/issues/65286) like performance, and sometimes it does not apply type rename...