Should I install an older version of Visual Studio to work on an old ASP.NET app?

Falanga, Rod, DOH 80

I prefer to use Visual Studio 2022, because I've been working with newer, .NET projects. However, I may be assigned to do some maintenance on an older, .NET Framework ASP.NET WebForms application. I've been familiarizing myself with the app this morning and am concerned with what I've found. The app is 10 years old. Over that time there's been several different developers who've worked on it, some of whom are no longer with us. There are 18 projects in the solution. There are 5 different .NET Frameworks in this solution; everything from .NET Framework 2 to .NET Framework 4.5.1. And what bothers me most is there's at least one package which I cannot find on NuGet. I've searched online for this package, with no success. (I found something similar in a GitHub repo, but it wasn't the same thing.)

So, my question is this. Given this situation, can I use VS 2022 to edit and maintain this solution or should I use some older version of Visual Studio?

Lan Huang-MSFT 25,556 Reputation points Microsoft Vendor

2024-04-19T02:47:04.26+00:00

Hi @Falanga, Rod, DOH,

Given this situation, can I use VS 2022 to edit and maintain this solution or should I use some older version of Visual Studio?

Old projects can also be maintained using VS 2022.Your problem is not with the VS version, but with the .NET Framework version.Older versions of the .NET Framework are no longer supported.

Microsoft .NET Framework - Microsoft Lifecycle

As the framework is updated, some packages and methods become obsolete.

Obsoletions in the .NET Framework class library

If you created your app using an earlier version of .NET Framework, you can generally upgrade it to .NET Framework 4.6.2, .NET Framework 4.7 and its point releases (4.7.1 and 4.7.2), or .NET Framework 4.8 easily.

Migrate to .NET Framework 4.8, 4.7, and 4.6.2
Falanga, Rod, DOH 80 Reputation points

2024-04-19T15:46:56.7066667+00:00

Hi @Lan Huang-MSFT ,

Thank you for your feedback. I'm glad that I can use VS 2022 to edit those old projects!

FWIW, I have argued multiple times, over the years, to upgrade those old projects off of unsupported .NET Frameworks, but my management has always vetoed my requests. :( Well, perhaps with this solution another attempt to just upgrade the project to a supported version of .NET Framework and whatever libraries that need to be upgraded accordingly, will work.

1 answer

Bruce (SqlWork.com) 56,526 Reputation points

2024-04-18T20:41:07.87+00:00

the default install of VS 2022 does not include the old framework, but you can install support. Unlike .net core, the old framework was very loose on version support. you can override in the web.config the version used. It will build, it just crashes if there is an incompatiability. VS 2022 will work as well as an earlier version. Some of the older designers if used may need to be installed.

you indeed may be using a nuget package that is no longer published. You just need a copy of the binary dll. Your app may also be using components only installed in GAC (especially before framework 4.5). Of course on a new machine, they may not be installed. You will need to track these down so they can be installed on the server separately. your package may also have been from codeplex which was used before nuget became popular. Unfortunately MS shut it down. there is a an attempt at an archive: https://codeplexarchive.org

once you get it to build and run, I'd update all the projects to 4.8. This also involves updating the nuget packages. This is less than trivial if some of the projects are pre 4.6. You should start with the master web project first. Updating the project file, config and nuget from 4.5.1 is rough. It's probably easier to create a new 4.8 web project and add the source code and nuget packages.

once the web project is 4.8 you can start updating the library projects. again you probably want the new project format, so create a new library and add files.

if you are using membership, be sure to read release notes. the encryption defaults changed, so you need to force the old behavior.
Please sign in to rate this answer.
Falanga, Rod, DOH 80 Reputation points

2024-04-18T21:15:13.5466667+00:00

Thank you, Bruce, for your response. I've got some follow-up questions I'd like to ask.

Unless I misunderstood you, it seems like I can use VS 2022 to edit the solution. However, I think you're recommending that I put .NET Framework 4.8 on my new machine (it may already be there, it is a Windows 11 Enterprise machine), then create a new repo, based only on .NET Framework 4.8, and copy everything over from the old repo into the new one. Once in the new repo I've got to upgrade all of the projects to .NET Framework 4.8. Have I got that correct? I hope so, because I'd rather do that then install 5 old .NET Frameworks onto this new machine.

As an aside, for reasons I've never been told, the habit here is to never upgrade any software solution or project. I don't know why, but there it is. I think we even have some production apps running on .NET Frameworks older the 2.

That one NuGet package is a major problem. About a year ago I tried to figure it out, as I said, but couldn't find it. Thank you for the link to that Code Plex archive! That may be useful. I hope I can find it there. When I looked at it before I couldn't figure out from its name, what the package was supposed to do. It's called SymphoniaPackager (and some similar named packages, which I assume are sibling packages). I bring it up here in hopes that you, or someone else reading this, may know something about it. There's no documentation on this project. (BTW, I remember CodePlex. I kinda miss it, but like the way that NuGet behaves better.)

FWIW, I'm sure that the server this app runs on, has all 5 of those .NET Frameworks installed. I'm not sure about .NET Framework 4.8, though. Isn't it the case that some intermediate .NET Frameworks need to be installed, before one can install .NET Framework 4.8?

I take it from your response that the Visual Studio project file changed by the time Microsoft came out with .NET Framework 4.8. I guess that's no surprise.

Last question, what did you mean by, "Unlike .net core, the old framework was very loose on version support..."?

Bruce (SqlWork.com) 56,526 Reputation points

2024-04-19T16:55:35.15+00:00

the old framework is update in place. so if you installed 4.8, there is no earlier 4.* to install. if you are using net 2.0 and .net 3.5, you may have to install the .net 3.5 runtime.

you may also need to install MVC 3, and Asp.net Web pages.

if you use .net core, say your app is .net 8, it can only use .net 8 libraries (or .net 2.0/2.1 common). with the old framework the runtime was not supposed to break between versions, so 4.8 project can call 3.5 library (though it may crash if incompatible).

in the old framework, the project files are the biggest difference between versions (other than later version having additional apis). if you build a 4.5 .net app and run on your box (where 4.8.1 is installed), it uses the 4.8.1 runtime.

this is unlike .net core. to run a 3.1 net core app, you need the 3.1 runtime installed. while .net core tends to bump the major, .net 8.0 and .net 8.1 (if one) would require separate runtime installs. only the patch version updating is supported without an app rebuild.

note: if you track the dll's you can build your own nuget package.

Falanga, Rod, DOH 80 Reputation points

2024-04-19T17:14:46.73+00:00

I've just checked my new machine. It only has .NET Frameworks 4.0 and 4.8 installed. So, that means may have to install .NET Framework 3.5. With 4.8 and 3.5 installed, will I be able to debug this app? There are 6 projects in the solution that are based on .NET Framework 2. :(

Falanga, Rod, DOH 80 Reputation points

2024-04-19T17:38:48.2133333+00:00

Hi Bruce,

You said that the biggest change, back in the .NET Framework days, was in the project files. I know that migrating from .NET 6 to .NET 8 is basically just an edit to the project file, so trivial. But I've no idea how to migrate a .NET Framework 2 project to .NET Framework 4.8. How do I do that?

Albert Kallal 4,651 Reputation points

2024-04-19T18:19:45.1033333+00:00

In most cases you can use vs2022. However, due to those older framework packages, I actually suggest you using 2019. In 99% of cases, you can increase (change) the older .net frameworks used to say 4.8, but you want to do this one project at a time, and build + test the project separate. Due to this issue of older frameworks, then 2019 does have better support, and while in "most" cases vs2022 is fine, your case could be an exception, since vs2022 is more "picky" about the versions of .net being used.

As for the older packages? They should exist in the current projects. In other words, you may well have to manually setup working references to the .dll assemblies, and it even doubtful that NuGet was even being used here.

So, I would open each project, and to upgrade such projects to say 4.8, then I would simple change the .net framework, and build. If that works, then you just upgrade the one project to 4.8. Do this for each separate project. THEN and only then would I try building the main project you have that includes the multiple projects. So, this changed + build of each project? This most likely will work better with vs2019.

Falanga, Rod, DOH 80 Reputation points

2024-04-19T19:02:13.9366667+00:00

Hey Albert,

Thank you for your reply. I'll have to go back and install VS 2019.

The dependencies are my greatest concern, especially for those .NET Framework 2 projects. I'm sure, like you said, that NuGet won't have any of those references. The prevailing thought where I work is, "If it ain't broke, don't fix it." In this case that guiding principle has resulted in the app being very difficult to build. Things change, updates to Windows happen, etc.

Your approach, if I understand it correctly, is for me to take each child project and migrated/build it separately. Then when all those are working, do the same thing with the main project, which will have links to the other 17 projects. Am I correct? If so, why do you suggest doing that?

And another question. I've never just built one project in a VS solution with multiple projects. I've always done the whole solution. How do I build just one project at a time?

Albert Kallal 4,651 Reputation points

2024-04-19T23:13:59.82+00:00

Ok, I was "already" under the assumption that you have multiple projects in one project right now. I mean, if that is NOT the case, then you want to hold off on combining multiple projects into one project UNTIL such time you have all the projects say running under .net 4.8. At that point, then opening the project with the multiple projects could simply then be also set to build with .net 4.8, and you would be quite much done.

In other words, it is assumed that you are/would open a given project. You then simple change the .net framework in the project settings to 4.8, and build. If that project builds ok, then you move on to the next project and do the same. So, you don't need to "copy" or "import" the older existing projects to update their current .net framework settings.

So, if you have multiple projects in that one solution? Then to open/use/work with the each of those projects? Then in VS you close that main project, and then simply open each project one at a time. Each project can with ease be opened 100% separably, and there is little reason to open that main project.

So, you open the first project, make sure it builds, and then try changing the .net framework to say 4.8. Now try building again. If not, fix errors until it builds.

Do the same for each of the other projects.

At that point, you go back to the main project, and change it's .net setting, and do a re-build all.

I mean, those multiple projects could not have made their way into that one main project without you having all and each of those separate projects. This in some ways is great, since then you can upgrade each individual project one by one, and then once done, you can now go back to the main project that includes all of those other projects.

So, I assume that you have this one project with multiple projects already. If you don't, then I would STRONG suggest you hold off on trying to have, add or use a new main project with all of the multiple projects added into that project. (you would do that AFTER you have all projects upgraded and working).

Falanga, Rod, DOH 80 Reputation points

2024-04-23T14:51:33.97+00:00

Well, I'm late to this application. I've no idea who started it, as that happened before I joined the organization. And given the fact that there's 5 different .NET Frameworks used among the 18 projects in this Visual Studio solution, I get the feeling a lot of people have contributed to it over the years. The thing that irritates me is why no one bothered to bring all the projects up to the same .NET Framework?

Thank you, Albert, you've given me a course to follow.

Bruce (SqlWork.com) 56,526 Reputation points

2024-04-23T17:13:43.3166667+00:00

the reason they did not update the projects is because it is work. if you look at the project files they have included to version specific build tools. also the binding in web.config need to updated with each nuget package update.

there is this horrible block of versions that need bcl packages added, but should be removed in later versions. there is also tricky update of httpclient going from pre .net 6.1 to later.

I done this several time with larger projects. the projects files and the final web.config are the biggest issues. also rebinding wcf references can be an issue (I often just do an undo and keep the original generated files).

given where you are I'd update the projects to the new simpler project files (netstandard2.0 or net48) and the c# 7.3 compiler, the lastest that the old framework supports.

to update the project, I unload (if its loads) and manually update the project file. You can use VS to generate sample project files. reload the project, then use VS to add the nuget packages back. (packages.config has the old list, you can delete when done).

hint: create a common place to put dll's you can not not find the source for.

the asp.net site requires the old format. use visual studio to create a new 4.8 project. save the old project files, you may need the path hints to find referenced dlls.

You don't state your starting point. Can you build the project as is? It's true vs 2019 is the friendlest version for old code. but once you can load and build in vs 2019, the project should work in vs 2022 with no changes (just the correct workloads need to be added).

Falanga, Rod, DOH 80 Reputation points

2024-04-23T17:48:33.3366667+00:00

Last year I tried to build the project, for another reason. I couldn't, but assumed it was because I didn't have all of the DLLs. Someone else has maintained that project for the last several years. I guess he's being reassigned and I'm getting stuck with it. I'll have to get those DLLs from him.

Bruce (SqlWork.com) 56,526 Reputation points

2024-04-23T20:08:24.81+00:00

older asp.net projects often used GAC installed libraries (include asp.net components). you may need to track these down an install the sdk. this is especially true with .net 2.0 and 3.* projects.

Falanga, Rod, DOH 80 Reputation points

2024-04-23T20:50:00.99+00:00

Dang, I'd forgotten about libraries being installed in the GAC. And that is certainly possible, since 6 projects are .NET Framework 2.
Sign in to comment