Melissa Treviño

I also see the missing configuration value here: 

Typo is being fixed here: #8266. I'll edit this issue's description describe the greater bug.

@drewnoakes and I looked at how these properties behave in the legacy world, for WPF and WinForms projects. The MyApplication feature has two modes of operation, one for WinForms and...

If loading a .NET Framework project with the new project system, the MyApplication feature doesn't appear to have the information it needs to identify whether the project is WinForms or...

I think the work remaining here is to incorporate unit tests to both WPF and WinForms scenarios, some of which are already in.

If the user goes: 1. Disable application framework. 2. Enable application framework, which creates that `StartupObject` property with `(None)` as its value. 3. Disable application framework. The `StartupObject` property will...

This is issue is yet to be addressed in the new Project Properties UI.

> I'm confused because there is seemingly contradictory expected behavior in the issue and then in the first comment. Could you clarify expected behavior I think my intent was to...

> Why would we have (None) for the StartupProject to begin with, when we're enabling the App Framework? We don't have it for the new experience, so we can move...

https://github.com/dotnet/project-system/pull/8419 addresses this and ensures we have the correct values set in the project file and myapp file as described in the last comment.