ASP.NET Core 3.1 web application throws error 500.30 when run on IIS Express, but not when using dotnet watch run

I had the same problem with IISExpress. The only way I could get ride of the 500.30 error, was to run the application in OutOfProcess mode. 

  <PropertyGroup>
    <TargetFramework>netcoreapp3.1</TargetFramework>
    <AspNetCoreHostingModel>OutOfProcess</AspNetCoreHostingModel>
  </PropertyGroup>

There is github issue about this problem.

Using 2.x versions of Microsoft.Extensions.* and Microsoft.AspNetCore.* packages in an ASP.NET Core 3.0/3.1 project is *not supported.

In my case i was depending on nuget package which was depending on Microsoft.AspNetCore 2.x.x. After removing the nuget the project ran without issues under IIS Express.

If anyone is still having this issue, you can try to remove dependencies with version 2.x because they are automatically resolved from the SDK.

Tags:

C#

Iis Express

Asp.Net Core

Related

React app error: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS phpunit, laravel: Cannot use "parent" when current class scope has no parent springdoc-openapi apply default global SecurityScheme possible? Retry failed jobs in github actions Volley request retry policy doesn't consider timeout NGINX read body from proxy_pass response Error: Please, upgrade your dependencies to the actual version of core-js@3 How to run a function when a route changes in angular? Return the last record in a One to many Eloquent Relation using Laravel Printing elements with VueJS using 3rd party libraries Installing ruby-2.1.2: Cannot load such file -- openssl (LoadError) ElasticSearch start up error - the default discovery settings are unsuitable for production use;

Recent Posts