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.
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.