1

We have migrated an application from Net version 3.5 to 4.8. The truth is that we are encountering many problems. Everything seems right, but it doesn't seem to work returns a 500 error without any more information. My approach is that it is not running with the correct version of Net. Therefore, install version 4.8 of the following link: Net 4.8 Framework for Windows Server 2016. It still doesn´t work. I still have my doubts, how can I know which version of Net 4.8 is using my application, considering that I do not have access to Windows Features?

Could you check this information from here?

Configuration APP

Improve this question
16
  • Usually before you deploy an app to a server you run it locally, right? Can u run the app in your dev environment? Usually with CLR 4.0 windows supports all .NET versions up to version 4.8. So you shouldnt run into any errors there. But please confirm the software runs with 4.8 at all since this is a major change Commented Apr 5, 2023 at 8:44
  • @Aaron. Yes, we test it first in local and it works fine. Many Thanks for your response. Commented Apr 5, 2023 at 8:45
  • Have you got some logging turned on to see where the error occurs? However please open IIS and check in the application pools the not working application (pool) and select advanced setting. There should be something regardig the .net version i suppose Commented Apr 5, 2023 at 8:48
  • @Aaron. I can´t see so much in the LOGs. There are a lot of information without meaning for me. In Advanced Settings I find "Net CLR Version = 4.0" "Pipeline Mode = Integrated". Many Thanks Commented Apr 5, 2023 at 8:59
  • The right solution is to publish application and install using setup.exe like any commercial software package. Publish updates the windows dll on deploy machine to match the build machine. A net application will only work if you deploy or use same version of net (including updates) on both build and deploy machine. Commented Apr 5, 2023 at 9:46

1 Answer 1

Reset to default
0

Seems like there may be two issues here.

First: Which versions of .net are installed and running on IIS. Check out this q to which versions are on IIS and are used by the AppPool. Which version of the .NET Framework is IIS using for my AppPool?

Secondly is possible (though not likely from what you described) that the web app is using a an older version of .net or maybe a library targeting an older version of .net If you built the app double check any libraries and DLLS to see what version they target. You can try Telerik's "justdecompile" tool (it's free) if you need to look at third party dlls.

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Thanks for your response. Net CLR is version 4 and We have migrated this project in local first and all libraries and DLLs looks fine.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.