Problem on server after upgrad from .NET 4.6 to .NET 4.8 (site is KO)

Question

Problem on server after upgrad from .NET 4.6 to .NET 4.8 (site is KO)

Wassim GHARSALLAOUI 20

Hello, We have just updated the version of an asp.net MVC project from .NET framework 4.6 to .Net 4.8. Following this, the solution compiles and works well locally whereas this is not the case after deploying the site. it no longer works on the server knowing that the .NET 4.8 version is installed on our server machine and the dependencies are up to date. Can you give me a lead and an idea, it's possible that I'm missing something? Thank you. error site

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Bruce (SqlWork.com) 85,201

System.Net.Http was reworked for net 4.6.1 and is part of the framework so you no longer include the package. you probably have a 4.6 project or nuget package that is dependent on the old package. You can fix up the projects or just a add a binding override in web.config

if it runs locally, than check the hint paths in the project files, they are probably out of date.

0 comments

2 additional answers

Answer 1

Michael Taylor 61,236

This is the generic error page so it doesn't provide any useful information. Enable custom errors in your app's web.config and then try again. You'll get a more detailed error message.

<system.web>
        <customErrors mode="On" />
</system.web>

Note that if you upgrade the .NET Framework then you must ensure all the web components are restarted. If you rebooted the server then that is sufficient. If you didn't, and a reboot wasn't required, then you have to restart multiple services.

Stop-Service w3svc
Stop-Service was

Start-Service w3svc

If that doesn't help then reregister ASPNET using aspnet_regiis -i.

Wassim GHARSALLAOUI 20 Reputation points

2024-02-01T17:03:38.4133333+00:00

Thanks for replying. But that didn't solve the problem for me. even by modifying the mode of the web config file but I always had OFF mode (I'm sure I'm pointing to the right file.)
Michael Taylor 61,236 Reputation points

2024-02-01T17:25:33.1766667+00:00

Maybe I didn't explain clearly. Set the custom errors ON. This enables detailed errors from the server. Then run your app again. Rather than getting the generic error page you'll get a detailed error about what is failing. That information is what is needed to figure out why your site is no longer working. Please post the details of that error page.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 2

Wassim GHARSALLAOUI 20

erreur .net

Michael Taylor 61,236 Reputation points

2024-02-01T18:48:34.4466667+00:00

So it cannot find System.Net.Http. That is part of the framework. To clarify you just updated the existing framework on the system. You did not deploy a new version of your app? If you did deploy a new version of the app then I'm going to say it is a binding redirect issue. If you have System.Net.Http in your output directory then you need to ensure you have a binding redirect that points to that version in your web.config file. If you don't have such a file then that would lean towards a bad environment. I would check the app pool settings in IIS to ensure you're targeting .NET 4. I would also check the web.config's compilation element to ensure the targetFramework is set properly and the httpRuntime for the same thing. Although these shouldn't really cause the error you're seeing.
AgaveJoe 31,706 Reputation points

2024-02-01T18:56:01.4033333+00:00

The error is telling you that your application cannot find System.Net.Http version 4.0.0.0 which is from 2015. Maybe you upgraded to the latest version but there is a reference in the web.config, a NuGet package is uses 4.0.0.0, or maybe project is using 4.0.0.0. Trying using NuGet to install the correct version of System.Net.Http for your projects. You can see the and check the version of System.Net.Http in the project references node in Visual Studio.