Printable View
Yet another ? about 2003/2005 LOL
A coworker informed me that I cannot install vb.net 2005 on the same machine as 2003. This has something to do with the 2.0 framework along side of 1.1.
Has anyone had any luck or dismay running these four on the same machine? I wanna start banging on 2005 but can't afford to have problems on my computer right now.
Yes and No. If you have already written 2003 code and you install 2005, then the 2003 will use the 2.0 framework and some 2003 code is not compatible. If you write 2003 code after its easier to test as you write. This is not a bug. You just need to see if the code is 2.0 compatible and not depreciated or discontinued.
No, not the code. I'm wondering if the four PRODUCTS are compatible on the same machine. Think of yourself as installing the frameworks and installing 2003 and 2005...will there be issues that will cause one or the other to screw up? This coworker says that his production machine has stopped being as responsive since he installed 2005 to test it. And, he couldn't start 2003 up until he reformatted his computer.
He must have installed 2005 "over" 2003 in the same directory? It installs by default to a different separate directory. Even the framework can co-exist side by side. It is a drain on your system if your system is not very fast and you install multiple IDEs. I have 2003 and VS 6 side by side and it slows down my system just a bit but then I am running a P4 2.8 high performance system.
Interesting...You're saying that simply HAVING them installed drains system performance? I can see if you run them simultaneousely but not just having them installed...Am I understanding you correctly?
Yes and no again. If you have a 40 gig hard drive and you fill it almost up with installing allot of programs, your using up the hd resource. That will slow down your system as a single program when needing to use a system file during startup of that program will take longer to start since it has to look through more system files, larger registry, etc.
Now if you have them all running the of course yes it will be more of a drain. The registered system files of a program get searched for first in the programs app dir, then windows, then system32, etc. until its found or not. This all takes time and resources away from your system.
I hope I have explained it correctly but this is basically the gist of it all. :)
RobDog888,Quote:
RobDog888
I have 2003 and VS 6 side by side and it slows down my system just a bit but then I am running a P4 2.8 high performance system
Have you noticed if you do not install all prerequisites, ie IIS, web stuff, etc. VS 6.0 will not fully load all components of previous projects?
I have repeated this behaviour several times, on a few different machines.
They seem fully compatible otherwise.... well 9x% anyway.
Nope, as I need all options loaded/installed for VS6 Ent. and VS.NET 2003 Ent. versions. I have no need for a limited install but maybe others have noticed something?
It sounds like there might be some advantage for me to have VS2003 on one machine, and VS2005 and VB6 on another.
You can have VS6 and .NET 2003 on one system but perhaps better to have 2005 on its own.
Darn, I currently have VS2003 on one system and VB6 on the other. Looks like I should add VS2003 to the system with VB6, and move to VS2005 on the other.
Or just make sure you have 2003 and 2005 on different systems and vs6 on both :D
I have both install on the same box with no trouble or performance loss. The only issue I see is that 2005 is a Beta so sometimes uninstalling is a ***** and it would be required in order to install the final build of 2005 when it comes out. For instance I had Beta 1 installed and had a hard time getting it uninstalled so that I could move to Beta 2.
I could be wrong about this, but I think you'll find that the reason you can have multiple versions of the .NET Framework installed is because apps that are built to target a particular version will only use that version. That means that if you install VS.NET 2003 and VS 2005 on the same machine then you will have versions 1.1 and 2.0 of the Framework installed, and apps built with each version of VS will use the corresponding version of the Framework. If you were to uninstall version 1.1 then apps built with VS.NET 2003 would not use version 2.0 but would just stop working. I'll test this when I get the chance and let you know for sure.
If you uninstall 1.1 then 1.1 applications would attempt to use 2.0 unless they encountered an error or were unable to JIT due to changes in the framework. BUT you would not be able to use VS 2003 anymore as it can only target versions of the Framework equal or lower than it (1.1 or 1.0). The 1.1 Framework is also a dependency for VS 2003.Quote:
Originally Posted by jmcilhinney
I read on MS a while ago that when you run your 2003 app it looks for the framework. If 2003 "finds" 1.1 only then it uses that (nless specified to use 1.0), but if it "find" 2.0 then it will use that. This is where the compatibility issues arise when having both 2003 and 2005 on the same system. Certain functions and methods are no longer in 2.0 so the 2003 code will bomb on it.
Actually, I just read here that a version 1.1 app will use version 1.1 in preference to version 2.0 if both are installed. Only if version 1.1 is not installed will it choose to use version 2.0, which should not present a problem for the majority of apps.
Edit:
Maybe that's what you were saying already and I just misinterpreted.
Yes, that is where I read it. But if you read the section "Application Load Mechanisms and Possible Issues" you can see that under certain circumstances it will use 2.0 when 1.1 exists and cause an issue depending on the code used. So my memory wasnt exactly as good as I thought but it seems that when it is targeted for 1.1 it will use 1.1 even when 2.0 exists. :)
i have 2003 and 2005 on my machine... and run both consecuitively(never had to spell that b4) no perfomance loss... nutin...
RobDog almost all of what you would build in VS will fit into the first row of that grid (1.1 stand alone) which as it states if they have both uses 1.1 but I think that doc spells out all the scenerios. Thanks!
I had a conversation this morning with that coworker. He informed me that the reason he had trouble was a bug in the 2.0 framework that was out at the time...It has been since fixed.
I installed 2005 Beta2 and the 2.0 framework on the my single production machine and so far, no problems.
Apparantley, that's all it was.
Can you have an app be not-targeted to a particualr framework version? I thought you had to select a version?