Deployment IIS .NET 6



I’m trying to deploy to production IIS 10, the simplest .net6 application (a page with a button).

I have done the following:
Created an “No Managed Code” Application pool named test6, Integrated Mode
Created C:\inetpub\test6 folder, gave Full permissions to IIS_IUSRS
Copied everything from my dev to that folder
Uncommented the lines in Web.config, have tried both
<aspNetCore processPath=”dotnet” arguments=”.\WisejMobileWebPageApplication1.dll” stdoutLogEnabled=”false” stdoutLogFile=”.\logs\stdout” hostingModel=”inprocess” />
<aspNetCore processPath=”.\WisejMobileWebPageApplication1.exe” arguments=”” stdoutLogEnabled=”false” stdoutLogFile=”.\logs\stdout” hostingModel=”inprocess” />
Created an application under my default site, named test6, pointing to the above folder and running in the test6 application pool

The result when I navigate to
a blank page in the browser, the text in my default.htm shows in the browser tab
if I open the console with F12 I see a red line where it tries to load wisej.wx
in the Event Viewer I see that the application has started successfully

Of course I tried this simple app after trying to deploy my real one. During that process I have
checked that the runtime and bundles are installed (6.0.6, both x86 and x64).
run the app from the command line and it runs.
tried explicitly running the x86 or x64 versions of dotnet
run the net48 version with the usual bin folder, it works alright

It looks like the problem is not in ASP.NET, the application runs, but wisej.wx cannot be accessed for some reason. I have attached some screenshots. You can access the app (the blank page) at

Please help,



  • You must to post comments

Hello again,

As Alaa pointed out, it was the order of the handlers. The publishing process had added the uncommented aspNetCore handler at the end.
<add name=”aspNetCore” path=”*” verb=”*” modules=”AspNetCoreModuleV2″ resourceType=”Unspecified” />
whereas the commented-out aspNetCore handler from the original wisej-provided web.config was on top. After I mover the uncommented handler on top, it worked.

A side effect I’m seeing now is the following. I have three wisej applications under my default web site. The test6 one runs ok. However, the other two show a popup message (attached) with the message:
Wisej failed to initialize for the following reason: Access to the path ‘C:\Windows\TEMP\Wisej 3\Applications\\ Wisej.Platform.QXDesktop.json’ is denied..
If I go to the temporary folder indicated by the message, I see several files, which I suppose are extracted automatically by the application. From the path to the folder, I suppose there is one folder created for each website-port combination. This one was probably created by the “test6” application, since in the security of the folder I see a “test6” user (the Application Pool I suppose). It sounds like the other two applications do not have permissions to do any work in that folder. I suppose that the right behaviour would be that each application created its own temporary folder.


  • You must to post comments

Hi Alex,

can you please send your web.config to and we´ll take a closer look?

Thanks in advance,

  • Alex Prinias
    Hi Frank, just sent it. Thanks! Alex
  • You must to post comments
Showing 2 results
Your Answer

Please first to submit.