Frameworks

[MMock]

I have some questions on frameworks. We are about to have two of our servers hosted and two of our other servers moved from their current hosting company to a better one. Simultaneously to that, we want to do some cleanup and understand what architecture and software we have on each box and what we really need.

I have a web application I wrote with visual studio 2005 so I thought it needed the .net 2.0 framework. I just looked at it on our "test server" (one of the servers we will be having hosted), and it is actually using the 1.1 framework - 1.1.4322 to be exact. Should that be changed to 2.0? And if nothing is using 1.1 anymore, should we "delete" it (or whatever you do to a framework to get rid of it...). At what point would we want to start using framework 3.5? Would I have to write different code?

Could performance issues be caused by having "too many frameworks?"

Note too that most of our websites, or at least the one I am primarily responsible for, is still side-by-side ASP pages and ASP.NET pages.

Thanks.

[gep13]

Hey,

There is no reason why you can't have all the frameworks installed on the same machine.

For instance, on my home machine, I have 1.1, 2.0, 3.0, 3.5 and the 4.0 Beta. I think I am right in saying that there isn't any performance implications on having them all there, but I have no evidence to back that statement up.

It really comes down to manageability and maintainability. We are in the situation at work that we have various web applications that target different frameworks, which means we have to have various versions of visual studio installed to support them. Since Visual Studio 2008 came out, this has got easier, since Visual Studio can target multiple frameworks, so ideally, we would want to move all the applications to 2.0, but this won't be happening for a while

If you can, I would suggest that you certainly suggest that the sites be transferred, not a complete re-write, but at least make them target 2.0.

As for 3.0 and 3.5, they are essentially bolt-on's to 2.0 to include things like LINQ, WPF and WCF, all of which are great, but if you are not using that functionality just now, then I would say stick with 2.0. The IIS configuration is the same regardless.

Hope that helps answer some of your questions.

Gary