VS2005 / VS2008B2 side-by-side issues
-
Hello, Does anyone know anything about problems with running VS2005 / VS2005B2 side-by-side? When I installed 2008B2, it seemed to break a number of things in 2005. Consider: I have an extensive 2005 C++/CLI project. Is used to build with 0 errors and 0 warnings. On the weekend I installed VS2008B2, I went back to 2005 and tried to rebuild my project. BOOM! 351 WARNINGS! First thing I did was check to make sure I was opening the project in 2005. I was. Did some research and found I was triggering a condition addressed by KB922271. The hotfix was not readily downloadable. You have to call MS tech support to obtain it. That's a load of crap. Rather than jump through hoops to get a hotfix, I uninstalled VS2008B2 and all related items (.NET 3.5, etc...). Surprise! my VS2005 project built with 0 warnings again. So the question is why is VS2008B2 install affecting my VS2005 installation??? I thought the whole point of .NET was that you could run multiple versions side-by-side without fear of side effects. So much for that! Your thoughs and comments are appreciated... Thanks.
Check this out http://blogs.msdn.com/astebner/archive/2007/06/22/3464822.aspx[^]
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson -
Check this out http://blogs.msdn.com/astebner/archive/2007/06/22/3464822.aspx[^]
Vasudevan Deepak Kumar Personal Homepage
Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis LevinsonThanks for the link, but that really doesn't address the issue. My problem isn't with file associations. My problem is once I install VS2008B2, my VS2005 projects don't build properly. He does mention that VS2005 and VS2008 can be run side-by-side. I guess I should assume from that statement that whatever issues I was experiencing with side-by-side operation with VS2008 beta 2 have been resolved???
-
Hello, Does anyone know anything about problems with running VS2005 / VS2005B2 side-by-side? When I installed 2008B2, it seemed to break a number of things in 2005. Consider: I have an extensive 2005 C++/CLI project. Is used to build with 0 errors and 0 warnings. On the weekend I installed VS2008B2, I went back to 2005 and tried to rebuild my project. BOOM! 351 WARNINGS! First thing I did was check to make sure I was opening the project in 2005. I was. Did some research and found I was triggering a condition addressed by KB922271. The hotfix was not readily downloadable. You have to call MS tech support to obtain it. That's a load of crap. Rather than jump through hoops to get a hotfix, I uninstalled VS2008B2 and all related items (.NET 3.5, etc...). Surprise! my VS2005 project built with 0 warnings again. So the question is why is VS2008B2 install affecting my VS2005 installation??? I thought the whole point of .NET was that you could run multiple versions side-by-side without fear of side effects. So much for that! Your thoughs and comments are appreciated... Thanks.
Xpnctoc wrote:
I thought the whole point of .NET was that you could run multiple versions side-by-side without fear of side effects.
What does SxS installs of the .NET framework have to do with having installs of VS 2005 and VS 2008? What warnings are you getting? Why are you trying to use a beta version of VS2008?? Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
-
Xpnctoc wrote:
I thought the whole point of .NET was that you could run multiple versions side-by-side without fear of side effects.
What does SxS installs of the .NET framework have to do with having installs of VS 2005 and VS 2008? What warnings are you getting? Why are you trying to use a beta version of VS2008?? Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
Mark Salsbery wrote:
Why are you trying to use a beta version of VS2008??
I am not currently using a beta. I am asking this question as basically a repeat of a question I posted almost 2 months ago but never really got a sufficient answer on. I uninstalled the beta long ago, and I'm trying to see what to expect before I go installing VS2008 RTM.
Mark Salsbery wrote:
What does SxS installs of the .NET framework have to do with having installs of VS 2005 and VS 2008?
Well they seem pretty related to me: .NET 1.1 installed with VS2003, 2.0 with 2005, and 3.5 with 2008. What I was saying was that I don't know what install was the culprit, but SOMETHING in the process messed up my .NET 2.0 projects.
Mark Salsbery wrote:
What warnings are you getting?
C4945. I don't have the exact wording, but it has something to do with not being able to import a class from an assembly because one already exists by the same name. KB922271 addresses this. The article suggests re-ordering the sequence in which assemblies are built. But I can't -- not to mention I shouldn't have to, because the project builds just fine on my other machine. The article also suggests turning off the "Copy Local" option for the references. But I don't want to. Nor should I have to since, again, having that option turned on gives me no problems when I build the project on my other machine. I think I have been in error on one count, though: I do not think it has anything to do with .NET 3.5 or VS2008 install. I think the problem is with .NET 2.0 SP 1. The reason I think this is that I was still able to generate the C4945 error after uninstalling .NET 3.5/VS2008 if I perform a "Rebuild Solution" action. I looked at the differences between my machines: The machine where I get the warnings has .NET 2.0 SP1. The machine that gives me no problem only has the original .NET 2.0 install. I uninstalled .NET 2.0 SP1, reinstalled the original .NET 2.0 build, reapplied the hotfix provided via KB922271, and VOILA! Everything is happy again. I can't remember how I ended up with .NET 2.0 SP1 on this machine. Is that an install option during the VS2008 installation routine? I don't remember deliberately installing that SP via Windows update, and I must not have, or it would also be on my other machine. So then the question is can I install VS2008 without being forced to updat
-
Mark Salsbery wrote:
Why are you trying to use a beta version of VS2008??
I am not currently using a beta. I am asking this question as basically a repeat of a question I posted almost 2 months ago but never really got a sufficient answer on. I uninstalled the beta long ago, and I'm trying to see what to expect before I go installing VS2008 RTM.
Mark Salsbery wrote:
What does SxS installs of the .NET framework have to do with having installs of VS 2005 and VS 2008?
Well they seem pretty related to me: .NET 1.1 installed with VS2003, 2.0 with 2005, and 3.5 with 2008. What I was saying was that I don't know what install was the culprit, but SOMETHING in the process messed up my .NET 2.0 projects.
Mark Salsbery wrote:
What warnings are you getting?
C4945. I don't have the exact wording, but it has something to do with not being able to import a class from an assembly because one already exists by the same name. KB922271 addresses this. The article suggests re-ordering the sequence in which assemblies are built. But I can't -- not to mention I shouldn't have to, because the project builds just fine on my other machine. The article also suggests turning off the "Copy Local" option for the references. But I don't want to. Nor should I have to since, again, having that option turned on gives me no problems when I build the project on my other machine. I think I have been in error on one count, though: I do not think it has anything to do with .NET 3.5 or VS2008 install. I think the problem is with .NET 2.0 SP 1. The reason I think this is that I was still able to generate the C4945 error after uninstalling .NET 3.5/VS2008 if I perform a "Rebuild Solution" action. I looked at the differences between my machines: The machine where I get the warnings has .NET 2.0 SP1. The machine that gives me no problem only has the original .NET 2.0 install. I uninstalled .NET 2.0 SP1, reinstalled the original .NET 2.0 build, reapplied the hotfix provided via KB922271, and VOILA! Everything is happy again. I can't remember how I ended up with .NET 2.0 SP1 on this machine. Is that an install option during the VS2008 installation routine? I don't remember deliberately installing that SP via Windows update, and I must not have, or it would also be on my other machine. So then the question is can I install VS2008 without being forced to updat
Ok, I'm following you (I think :))... You've mentioned VS2008B2 - If you ever had beta 2 installed then first make sure you've uninstalled EVERYTHING from that beta, as outlined here: Uninstalling Visual Studio 2008[^] I would go one step further and uninstall all .NET framework versions, then re-install any .NET 1.x versions desired and .NET 2.0 SP1, all from the redistributables. (I'm pretty sure a .NET 3.x installer is going to update 2.0 to SP1 anyway - may as well do it from the start - plus this gets rid of any monkey business from a previous pre-release .NET 3.5 install) At that point, your VS2005 should work properly. If so, install VS2008 RTM. I never had the specific issue you're dealing with, but I know the prelease .NET 3.5 install (right up to the release candidate) caused problems, including killing the VS 2008 RTM install. I currently am experiencing no problems with 2005 and 2008 SxS. Good luck :) Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
-
Ok, I'm following you (I think :))... You've mentioned VS2008B2 - If you ever had beta 2 installed then first make sure you've uninstalled EVERYTHING from that beta, as outlined here: Uninstalling Visual Studio 2008[^] I would go one step further and uninstall all .NET framework versions, then re-install any .NET 1.x versions desired and .NET 2.0 SP1, all from the redistributables. (I'm pretty sure a .NET 3.x installer is going to update 2.0 to SP1 anyway - may as well do it from the start - plus this gets rid of any monkey business from a previous pre-release .NET 3.5 install) At that point, your VS2005 should work properly. If so, install VS2008 RTM. I never had the specific issue you're dealing with, but I know the prelease .NET 3.5 install (right up to the release candidate) caused problems, including killing the VS 2008 RTM install. I currently am experiencing no problems with 2005 and 2008 SxS. Good luck :) Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
OK, I don't know what the heck is going on. I did what you said -- uninstalled everything, including all versions of .NET. Then I reinstalled .NET 1.1 and 2.0. Then I tried building my project. But I still get all those warnings. So then I tried reinstalling the KB922271 hotfix. That still didn't fix things. I guess my problem isn't actually VS2008 or .NET 3.5. But I'm still faced with a serious dilema: I have 2 machines with .NET 2.0 on them. One machine builds my project perfectly. The other produces 351 C4945 errors. I'm still going to say that somehow, somewhere, 2008 Beta 2 screwed up my machine. It is WAY TO MUCH of a coincidence that all these problems started after I installed 08B2 a couple months ago. Even though I guess I have little choice at this point but to reformat my hard drive and reinstall EVERYTHING if I expect this project to ever build properly on this machine again. Reading through all the articles and forums on MS website and independent websites, it looks like the cause of the issue was never found, and it doesn't seem MS really intends to solve it since they're on a new version of VS on the whole. I reread the hotfix article, and it mentioned that it pertained to using command-line builds. So from the IDE perspective, this issue was NEVER solved. I guess I should just count myself lucky that I have one machine that builds the project correctly. Is there anyway to just supress that warning message build-wide? For the record, I have read numerous posts in other forums where other users have this problem. It's all centered around having a C++/CLI application reference one or more C# assemblies. OK. I better go. I can feel my blood pressure rising. I've had to do everything I can to keep from filling this post with explitives.
-
OK, I don't know what the heck is going on. I did what you said -- uninstalled everything, including all versions of .NET. Then I reinstalled .NET 1.1 and 2.0. Then I tried building my project. But I still get all those warnings. So then I tried reinstalling the KB922271 hotfix. That still didn't fix things. I guess my problem isn't actually VS2008 or .NET 3.5. But I'm still faced with a serious dilema: I have 2 machines with .NET 2.0 on them. One machine builds my project perfectly. The other produces 351 C4945 errors. I'm still going to say that somehow, somewhere, 2008 Beta 2 screwed up my machine. It is WAY TO MUCH of a coincidence that all these problems started after I installed 08B2 a couple months ago. Even though I guess I have little choice at this point but to reformat my hard drive and reinstall EVERYTHING if I expect this project to ever build properly on this machine again. Reading through all the articles and forums on MS website and independent websites, it looks like the cause of the issue was never found, and it doesn't seem MS really intends to solve it since they're on a new version of VS on the whole. I reread the hotfix article, and it mentioned that it pertained to using command-line builds. So from the IDE perspective, this issue was NEVER solved. I guess I should just count myself lucky that I have one machine that builds the project correctly. Is there anyway to just supress that warning message build-wide? For the record, I have read numerous posts in other forums where other users have this problem. It's all centered around having a C++/CLI application reference one or more C# assemblies. OK. I better go. I can feel my blood pressure rising. I've had to do everything I can to keep from filling this post with explitives.
:( bummer. Beta versions are always sketchy. I suppose most people won't use/try them on production machines (except in a VM). If I think of anything else to try I'll let you know! Good luck, Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
-
:( bummer. Beta versions are always sketchy. I suppose most people won't use/try them on production machines (except in a VM). If I think of anything else to try I'll let you know! Good luck, Mark
Mark Salsbery Microsoft MVP - Visual C++ :java:
I solved the problem. In the project "References" for the main C++/CLI project, the KB article says to set the "Copy Local"/"Copy Local Dependencies" options to "false". As I said, I did that but it didn't work, and on my other machine where the project builds perfectly all those are set to "true" anyway. So then last night I just though about the warning message: "Cannot import symbol ... from assembly ... because symbol was already defined in assembly ..." In the message the first and second names assemblies are the same. OK. Somehow the assembly is getting included in the solution before it is actually being referenced. So then the the project references section I noticed there was these options "Use Dependencies In Build" and "Use In Build". To me it sounds like those options need to be enabled in order for the main project to be able to use the assemblies. But what the heck? So I set THOSE options to "false" and set the "Copy..." options back to "true". Well SON OF A GUN! The solution builds without a single warning message. I don't know why it works. I mean, it kind of makes sense in that the C++/CLI main project references C# assemblies A, B, and C, but assembly C also references assembly A. So I can see where assembly A might already be brought in by assembly C, so I get the warnings when the main app tries to re-reference assembly A. But where logic breaks down is that, again, I do not get these messages when I build the same project on my other machine. Based on this, maybe you have some idea what's going on under the hood to cause this? Thanks.
-
Hello, Does anyone know anything about problems with running VS2005 / VS2005B2 side-by-side? When I installed 2008B2, it seemed to break a number of things in 2005. Consider: I have an extensive 2005 C++/CLI project. Is used to build with 0 errors and 0 warnings. On the weekend I installed VS2008B2, I went back to 2005 and tried to rebuild my project. BOOM! 351 WARNINGS! First thing I did was check to make sure I was opening the project in 2005. I was. Did some research and found I was triggering a condition addressed by KB922271. The hotfix was not readily downloadable. You have to call MS tech support to obtain it. That's a load of crap. Rather than jump through hoops to get a hotfix, I uninstalled VS2008B2 and all related items (.NET 3.5, etc...). Surprise! my VS2005 project built with 0 warnings again. So the question is why is VS2008B2 install affecting my VS2005 installation??? I thought the whole point of .NET was that you could run multiple versions side-by-side without fear of side effects. So much for that! Your thoughs and comments are appreciated... Thanks.
RTM versions of the .Net framework are SxS compatible with previous version of the framework. As far as I’m aware, even the Beta versions of the .Net framework are SxS compatible with previous versions of the framework. However, Beta versions of framework 3.5 are not SxS compatible with the RTM version of .Net 3.5. See this article[^] for more info. However, that doesn’t appear to be the problem you’re experiencing. KB922271[^] talks about a problem where the ‘Copy Local’ setting in Visual Studio projects causes an issue with MSBuild.exe. Is that the problem you’re having? I know it’s frustrating when a hotfix isn’t publicly available and luckily that isn’t the case for all hotfixes. When Microsoft makes a hotfix available only through professional services this is usually because they don’t want the hotfix widely distributed. Why? Because hotfixes are eventually rolled into larger service packs or fixed before a product is released to market. Even when a fix is publicly available they’re usually accompanied by a message like: “A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.” The issue you’re having is likely already addressed in the release version of Visual Studio 2008, which is currently available on MSDN. I know VS takes a while to install / uninstall (I was just at the Houston InstallFest last night), so when you’ve got some time you might try it again with the RTM version. I hope it works for you.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software. -
RTM versions of the .Net framework are SxS compatible with previous version of the framework. As far as I’m aware, even the Beta versions of the .Net framework are SxS compatible with previous versions of the framework. However, Beta versions of framework 3.5 are not SxS compatible with the RTM version of .Net 3.5. See this article[^] for more info. However, that doesn’t appear to be the problem you’re experiencing. KB922271[^] talks about a problem where the ‘Copy Local’ setting in Visual Studio projects causes an issue with MSBuild.exe. Is that the problem you’re having? I know it’s frustrating when a hotfix isn’t publicly available and luckily that isn’t the case for all hotfixes. When Microsoft makes a hotfix available only through professional services this is usually because they don’t want the hotfix widely distributed. Why? Because hotfixes are eventually rolled into larger service packs or fixed before a product is released to market. Even when a fix is publicly available they’re usually accompanied by a message like: “A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.” The issue you’re having is likely already addressed in the release version of Visual Studio 2008, which is currently available on MSDN. I know VS takes a while to install / uninstall (I was just at the Houston InstallFest last night), so when you’ve got some time you might try it again with the RTM version. I hope it works for you.
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.Thanks for your response. Per my last response in my thread with Mark Salsbery, I have managed to resolve the issue. In short, both my main app (C++/CLI mixed mode) and one of my assemblies (C#) were both referencing another assembly (also C#). So when I build the main app, the double reference is what throws the C4945 errors. I did ultimately obtain the hotfix, but that did not help. However, even though my problem was in the IDE, the KB aritcle did get the thought process rolling. Instead of settings the "Copy Local..." options to false, I left those as "true" and set the "Use... in build" options to "false". That solved the problem. The reason I thought it might have something to do with installing 08B2 SxS is that was when I started receiving the C4945 errors in my 2005 project. To this day, on my 2nd machine -- where I never installed anything to do with 2008 -- I do NOT have to set the "Use...in build" options to "false", and I do NOT get the C4945. That's why I theorize that installing the beta messed something up SOMEWHERE inside my machine that even a full manual uninstall could not fix. However, all is well that ends well. I did uninstall the beta per the instructions on the MS website, and I have installed the RTM and am using it successfully. I still have to change my reference settings when I work on that 2005 project from machine to machine, but at least now I know how to fix it :)
-
Thanks for your response. Per my last response in my thread with Mark Salsbery, I have managed to resolve the issue. In short, both my main app (C++/CLI mixed mode) and one of my assemblies (C#) were both referencing another assembly (also C#). So when I build the main app, the double reference is what throws the C4945 errors. I did ultimately obtain the hotfix, but that did not help. However, even though my problem was in the IDE, the KB aritcle did get the thought process rolling. Instead of settings the "Copy Local..." options to false, I left those as "true" and set the "Use... in build" options to "false". That solved the problem. The reason I thought it might have something to do with installing 08B2 SxS is that was when I started receiving the C4945 errors in my 2005 project. To this day, on my 2nd machine -- where I never installed anything to do with 2008 -- I do NOT have to set the "Use...in build" options to "false", and I do NOT get the C4945. That's why I theorize that installing the beta messed something up SOMEWHERE inside my machine that even a full manual uninstall could not fix. However, all is well that ends well. I did uninstall the beta per the instructions on the MS website, and I have installed the RTM and am using it successfully. I still have to change my reference settings when I work on that 2005 project from machine to machine, but at least now I know how to fix it :)
Good deal man. Glad you got it fixed (for the most part anyway).
My posts may include factual data, educated guesses, personal opinion and dry humor. They should not be treated as an official Microsoft statement.
Sites of Interest: MSDN Events | US ISV Team Blog
Are you on Facebook? Check out the group My Company Writes and Sells Software.