.Net Core 3.1 App not starting automatically in IIS after deployment

Asked Aug 24 '20 at 14:39

Active Aug 24 '20 at 14:39

Viewed 706 times

I migrated an Asp.net core web app from .net core 2.2 to 3.1 and deployed it to IIS. The app was running automatically on 2.2 with the below settings but is not running until an API call is made.

I had the AppPool settings set to

.Net Clr Version: v4.0 StartMode: Always Running Idle Timeout: 0

And the WebApp Settings EnablePreload: true

Although I found nothing being changed regarding hosting on Microsoft.

Has anyone also faced such issues? Any help here would be appreciated

asked Aug 24 '20 at 14:39

Manas Singhal

1

Did you check your launchsetting.json file ? – Afshin Aug 24 '20 at 14:43
Please see my IIS check-list just to make sure everything is OK. Net Clr Version: v4.0 looks suspicious, but I don't have an IIS server right now to compare with. https://stackoverflow.com/a/63466234/14072498 – Roar S. Aug 24 '20 at 14:46
I compared with your link and changed it to NoManagedCode. It didn't work although. I copied the settings which worked for .NetCore 2.2 – Manas Singhal Aug 24 '20 at 16:04
Have you installed latest hosting bundle for asp.net Core 3.1, because your app will need it. – Roar S. Aug 24 '20 at 16:08
yes that is in place – Manas Singhal Aug 24 '20 at 16:19
Can you add the generated web.config to your question, just want to check it is ok. – Roar S. Aug 24 '20 at 16:20
Added AppInitialization section in system.webserver with following body – Manas Singhal Dec 02 '20 at 17:33

.Net Core 3.1 App not starting automatically in IIS after deployment

0 Answers0