Installing VS2005 beta 2 gives me an error at setup.exe saying I must uninstall VS2003 pro. Just to restate, it's not asking to uninstall 2005, it definately says 2003 What's up with that !!!!
Same here. I get a nice dialog on autorun from the Beta 2 (April) release, stating VS 2003 needs to be removed.
Ent Architect VS2003 7.1.3088 XP Pro + SP2
It also warns about me about VS 2005 and SQL as I have the Feb CTPs here as well which I know need to go, but VS 2003 is a big issue. Migrations and testing will just not happen right now for me if you need two machines.
I am doing some investigation here to see if we can repro this problem. I believe there should be no block for VS2003 ENT and that the only blocks should be for VS2005 previous builds.
Can you try running Aaron's tool to remove old WHidbey builds and then see if install works I think we may just have the incorrect error message in the UI and that the actual problem is that we are detecting some Whidbey component.
This is bad news. Both products live in different directories. What is the conflict here and why does this conflict exist This is a design flaw. I certainly hope this is fixed for RTM or many will have to live without 2005 for a while.
Must uninstall VS2003?
ryanlcs
What version of 2003 Pro Is this an RTM version or a Beta version Also, what OS are you on
Thanks.
deval bhavsar
Same here. I get a nice dialog on autorun from the Beta 2 (April) release, stating VS 2003 needs to be removed.
Ent Architect VS2003 7.1.3088
XP Pro + SP2
It also warns about me about VS 2005 and SQL as I have the Feb CTPs here as well which I know need to go, but VS 2003 is a big issue. Migrations and testing will just not happen right now for me if you need two machines.
MetroP
Retail MSDN version.
XP Pro SP2
ALso, I'm trying to install the Testing Suite version of Beta2.
kasperstorm
Can you try running Aaron's tool to remove old WHidbey builds and then see if install works I think we may just have the incorrect error message in the UI and that the actual problem is that we are detecting some Whidbey component.
http://blogs.msdn.com/astebner/archive/2005/04/25/411974.aspx
Please let us know if this works.
Bret Grinslade
VS/.NET Framewor Setup Team
grumpy3b