Closed halter73 closed 7 years ago
To report new issues, use the Report a Problem tool. The GitHub Issue Tracker for the aspnet/Tooling repo is now deprecated in favor of the Report a Problem tool.
If you encounter a problem with Visual Studio, we want to know about it so that we can diagnose and fix it. By using the Report a Problem tool, you can collect detailed information about the problem, and send it to Microsoft with just a few button clicks. See here for more details.
I opened TFS 473884 just in case, since it seems to be valid issue and we might want to consider it sooner.
This has been fixed in an upcoming update of Visual Studio
@BillHiebert, what version of Visual Studio has the fix? I'm on VS 2017 v15.5.7 and can still repro this behavior.
@abpiskunov, can you provide a link for "TFS 473884", so I can view the details? Assuming it's a public bug repo.
It is internal bug. It was fixed on 8/15/2017.
Given the launchSettings.json and Program.cs below, it seems that the ASPNETCORE_HOSTINGSTARTUPASSEMBLIES environment variable is set incorrectly when launching both the "IIS Express" or "WebApplication1" profiles from VS 2017 26730.0.d15rel and dotnet sdk 2.0.0-preview3-006889.
Expected output for "IIS Express" profile launched from VS:
Actual output for "IIS Express" profile launched from VS (App Insights is missing):
Expected output for "WebApplication1" profile launched from VS:
Actual output for "WebApplication1" profile launched from VS (HostingStartup1 is missing):
Actual output for "WebApplication1" profile launched using "dotnet run" (Behaves as expected)
launchSettings.json
Program.cs