Ulisses, I tried your app with IIS and the web.config we provide and it works without issues and without changes. The web.config we provide is setup to work with the project as-is. Please note that if you have IIS use the same target directory and run the app it will lock the binaries.
<aspNetCore stdoutLogEnabled=”false” hostingModel=”InProcess” processPath=”bin\Debug\net6.0\WisejWebPageApplication1.exe” arguments=”” />
Works.
If you want to use the publishing tool to consolidate the build, all you need to do is change the processPath in web.config. Also the publishing tools has many other options that you have to be aware of regarding the .NET 6 runtime itself. The documentation is all on msdn, it’s messy and unclear but that’s what it is from Microsoft.
It worked, Luca! It was the unmanaged app pool configuration.
Thank you very much!
Luca, I followed the following steps:
1 – Install ASP.NET Core Hosting Bundle: https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-6.0.4-windows-hosting-bundle-installer
2 – Create folder C:\inetpub\wwwroot\wisej3core
3 – Open IIS
4 – Add application ‘wisej3core’
5 – Open attached file (WisejWebPageApplication1.zip)
6 – Publish it
7 – Copy files to C:\inetpub\wwwroot\wisej3core
8 – Uncomment lines in web.config
9 – Open http://127.0.0.1/wisej3core/
Thank you, Luca. I uncommented the lines, but unfortunately this error is occurring.
The same as any ASP.NET Core app.
ASP.NET Core doesn’t use the IIS pipeline anymore. We are updating our deployment documentation, in the meantime you can use any resource that is available for ASP.NET core apps. https://docs.microsoft.com/en-us/aspnet/core/tutorials/publish-to-iis?view=aspnetcore-6.0&tabs=visual-studio
To make it easier we provide a web.config that is ready for IIS. See the comments in the web.config file. You basically have to enable an IIS handler that plays in between IIS and your ASP.NET Core app. We didn’t change this, it’s all Microsoft doing…
Please login first to submit.