 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C# / January 2008depencency problem in vs2008 setup project
Hi I recently switched over to VS2008 and had to create my first setup project (in VS2008) for an already existing project. So I had Visual Studio convert the existing solution, then added a setup project to it. I made sure that the runtime version of the upgraded project was set to 2.0 as I'm currently not using any language features beyond 2.0. After creating the setup project, I went into its properties and changed the dependencies to only include Windows Installer 3.1 and .NET 2.0. I shipped out the result of the setup project to a client, who only had .NET 2.0 installed on their machines. They soon found out that they couldn't install my app on their machines without upgrading to .NET 3.5 - the setup, even though I told it to only require .NET 2.0, would complain that v3.5 was not present and refuse to continue. I suppose I must've missed a flag somewhere but I can't figure out where so any ideas would be welcome. Regards Stephan Either its a bug or you didn't save the target. Can you reship the software? (Tall order but I think it's the only way unless you want to require your users to install an uneeded framework). Specifying a target does just that, it compiles for the target. As far as I am aware, a 2.0 target does not require a 3.5 run-time.  SignatureRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The O.W.C. Black Book, 2nd Edition Exclusively on www.lulu.com/owc $19.99 ------------------------------------------------------- > Hi > [quoted text clipped - 17 lines] > Regards > Stephan Alvin My Solution contains two project.. the application itself (definitely set to 2.0 target.. I had people run the compiled output on machines with only the 2.0 runtime installed and it works just fine), and the setup project (I can't find any framework target version there.. am I missing it?). I even removed the entire dependency check from the setup project but the results are the same - the setup refuses to proceed unless the 3.5 framework is installed. I'll now create a new setup project in Visual Studio 2005 and ship that to the client as a workaround, but either I'm missing a target version in the setup project, or Visual Studio 2008 incorrectly identifies the 3.5 runtime as dependency in the setup project it creates. Regards Stephan On Jan 17, 1:45 am, "Alvin Bruney [ASP.NET MVP]" <www.lulu.com/owc> wrote: > Either its a bug or you didn't save the target. Can you reship the software? > (Tall order but I think it's the only way unless you want to require your [quoted text clipped - 10 lines] > The O.W.C. Black Book, 2nd Edition > Exclusively onwww.lulu.com/owc$19.99 Interesting problem. I'll keep an eye on this. SignatureRegards, Alvin Bruney [MVP ASP.NET] [Shameless Author plug] The O.W.C. Black Book, 2nd Edition Exclusively on www.lulu.com/owc $19.99 ------------------------------------------------------- > Alvin > [quoted text clipped - 33 lines] >> The O.W.C. Black Book, 2nd Edition >> Exclusively onwww.lulu.com/owc$19.99 Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.