Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations biv343 on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VS2008 install package requirements

Status
Not open for further replies.

NESWalt

Programmer
Oct 8, 2007
99
US
We're using VS2008 Team Suite and still doing a lot of 2.0 development. I have a windows service that we need to install on a 2003 Server box that only has 1.1 and 2.0, and we can't install 3.x due to some incompatibilities that our network team discovered.

Whenever I try to install the package, despite having changing prereqs to 2.0 only, and the package/setup is targeting 2.0, the setup still requires 3.5 to be installed.

Is there a switch/option somewhere that I am missing to not require 3.5 even if the assemblies being installed don't require 3.x?

What's strange is that I have another service developed in 2008 and packaged the same way and it installs fine without requiring 3.5... As a matter of fact, I just rebuilt that program and deployed today to the same server with no issues.
 
What setup tool are you using?

I believe the one that comes with VS.NET tries to install v3.5 as part of it's bootstrap process, no matter what version the assemblies you're installing are targeting.

Another possibility is that you've got one or more assemblies that still say '3.5' instead of '2.0'

Chip H.


____________________________________________________________________
www.chipholland.com
 
Yes, I'm using the Setup tool that comes w/ VS.

What's strange is that I have another project that is built using the same tool and don't have this problem. What's more is that I can XCopy install the program to that server and it runs fine.

This is a good "solution" for now for me, but it violates are practices guidelines and I'll have to figure it out. The only other thing I can think of since it is 2.0 is to load the C# proj in VS2005 and build a setup there for it.
 
Hear that? That's the sound of me kicking my own butt...

In the Launch Conditions, it was still looking for version 3.5.21022 instead of 2.x... As soon as I changed that back to 2, it worked!
 
Glad you figured it out.
:)

Chip H.


____________________________________________________________________
www.chipholland.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top