Oneguy23
Results
1
comments of
Oneguy23
Confirming same issue here, when ASPNETCORE_ENVIRONMENT is Local. VS 17.1.0. Changing ASPNETCORE_ENVIRONMENT to Development "fixes" the issue, but would prefer not to have to make that switch.