4.60.5 installation

We are setting up a new install of 4.60.5 and the install would not work. It looks like the download link in the documentation is linking to an older version of the .net hosting bundle.

The  link should be updated in the documentation to go to the newest version. After installing the newest version of the hosting bundle the installation worked immediately.

Current link goes to 7.0.5
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-7.0.5-windows-hosting-bundle-installer

New link should go to 7.0.14
https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/runtime-aspnetcore-7.0.14-windows-hosting-bundle-installer

Strictly speaking it should not matter - I have 4.6.5 running on 7.0.1
What was the problem / error you had ?

The error was related to the web.config file. I don't remember exactly what the error was. All I did was install the newer version 7.14 and the install started immediately. I didn't reboot the server or even iis reset. Maybe it was just an an anomaly. Ill try another install tomorrow with 7.05

OK. with NOPcommerce 4.60.5 there is a web.config issue from the Visual studio version when installing on server 2019   - just spent some time resolving.  

This line seems to be the issue

<aspNetCore requestTimeout="23:00:00" processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" forwardWindowsAuthToken="false" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" startupTimeLimit="3600" hostingModel="InProcess">
    </aspNetCore>  

the above is from NOP4.60.5 Clean install - the process path looks to me to be the issue when moving to the server with the web.config - works fine with local visual studio but not with MS windows server 2019.  

I have also found and learnt from 4.50.3 the web.config and the following statement can be an issue and I remove from my web.config to put on the server.. will work with visual studio... but not server

<!-- Protects against Clickjacking attacks. ref.: https://www.owasp.org/index.php/HTTP_Strict_Transport_Security_Cheat_Sheet -->
        <add name="Strict-Transport-Security" value="max-age=31536000; includeSubDomains" />

Please check me out at https://www.hudzinski.com - if anyone wants to buy me a coffee for this fix I will send you my paypal page.  

Sincerely Your NOPCommunity Pal

Trevor

tee2022 wrote:
Where did this line come from - of course it would need the variables set to work correctly

Recent versions line (back to v4.4) is
    <aspNetCore requestTimeout="23:00:00" processPath="dotnet" arguments=".\Nop.Web.dll" forwardWindowsAuthToken="false" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" startupTimeLimit="3600" hostingModel="InProcess">