Reputation: 366
I believe I've narrowed this down to a configuration error, but I can't find where the error lies.
Steps to reproduce:
IIS Express starts, but when I navigate to the https://localhost:XXXXX/
page, I get an HTTP 500 error.
Things I've tried:
Nothing seems to change the result. This same method works just fine with the IIS Express setup I have at my office, but I can't go there right now. Remoting in is slow enough that it's inconvenient at best, and impractical at worst.
Upvotes: 1
Views: 1872
Reputation: 366
It would appear that there are some outstanding issues with IIS Express and Rider 2020.3, as can be seen in issue RIDER-55665, though unlike the user here I was unable to fix the problem with the steps provided. It seems as though rolling back from Rider 2020.3 back to 2020.2.x fixes the problem.
Upvotes: 0
Reputation: 11
enter image description hereI recommend you to restart the w3svc service with the following command in the console: net stop was / y net start w3svc
If you still have the same problem, it is better to run the application with dotnet so that it gives you more details of the problem in the console:
dotnet wNameApplication.dll
Try changing the section in csproj (edit with a text editor)
<PropertyGroup>
<TargetFramework>netcoreapp2.2</TargetFramework>
<AspNetCoreHostingModel>InProcess</AspNetCoreHostingModel>
</PropertyGroup>
to the following ..
<PropertyGroup>
<TargetFramework>netcoreapp2.2</TargetFramework>
<AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel>
<AspNetCoreModuleName>AspNetCoreModule</AspNetCoreModuleName>
</PropertyGroup>
Upvotes: 0