CODEWITHSUNDEEP
asp.net.net.net-3.5.net-4.8asp.net-webpages
Subhajeet Paria
Subhajeet Paria

Reputation: 99

Framework upgrade from .net 3.5 to .net 4.8

I'm working with one of my clients wherein they are having a few application still written on .net framework 3.5. Though we still have support for .net 3.5, client wishes to upgrade the framework to 4.8. There are no plans to migrate to core/.net 6 as of now but to upgrade to framework's latest version 4.8.

I'm looking for some pointers to migrate an application from 3.5 to 4.8, what could be the runtime changes/retargeting changes/breaking changes. It would be of great help if someone could give me a roadmap to address the problem - where to start from, what details to look into etc. I searched a lot and could not get any specific pointer for my use case. Please help.

Thanks in advance!

Upvotes: 1

Views: 6593

Answers (1)

Albert D. Kallal
Albert D. Kallal

Reputation: 49264

Well, in most cases, you should be able to simple set the project up to say .net 4.8 (or 4x). But, you might as well go all the way.

You WILL however has to download and install .net 4.8 on the web server. So, on your developer computer, you most likly do have .net 4.8. But, don't forget to download + install .net 4.8 on the web server (or if it is a hosted plan, find out what is the level of .net they support).

So, for the most part, you should be able to simple in your project, set it as 4.8, and see if it compiles. You have a VERY good chance it will.

That would be this setting project->"my project name properties"

enter image description here

So, the above for the most part should make things work.

Also, once you done the above, (then re-build all). You want to check web.config, and this setting:

<httpRuntime targetFramework="4.8" maxRequestLength="2000000"/>

As noted, you also have to check/ensure that the web hosted server (if this is not a on-site server) also needs the .net frameworks to be downloaded and installed. Often they already are but you want to check that.

It also possible that you are using a asp.net web site as opposed to a asp.net web site application, and thus the above steps do change somewhat.

Upvotes: 3

Related Questions