Project-system: Class Libraries show up in debug startup project list

[davkean]

This list is supposed to show projects that can be launched (so the user can quickly switch start up projects), neither of these projects can be launched:

[basoundr]

Blocked by VSO bug 389597

[JohannZhu]

Any updates on this issue? Finding one single executable project from dozens of projects is not funny... And I know some teams have hundreds of projects...

[moginheden]

I'm not sure if this is the same bug, but I was directed here when trying to figure out why my web project is NOT in the startup list, (but, a CLI and a Windows application are.)

[mmihaly]

We're migrating to .Net Core, and this is very annoying, hopefully it gets fixed soon.

[davkean]

We need to do two things:

1) Unregister the existing debugger launch providers that we're not using via the opt out here: https://devdiv.visualstudio.com/DevDiv/_git/CPS/pullrequest/219892. This will also fix https://github.com/dotnet/project-system/issues/6140.
2) Make our debug launch provider actually provide a useful result from IsDebuggableAsync, _or_ implement it terms of another method.

[4lexKislitsyn]

Additional information: VS2019 doesn't show .NET Framework's Class Library projects. So it excludes .NET Framework ASP.NET projects.

It's problem when you have solution with .net core and .net framework ASP.NET projects.

[jjmew]

This is a top feedback item hence giving it high priority

[davkean]

Reopen based on the revert here: https://github.com/dotnet/project-system/pull/6402.