I've never trusted the Project Output options as input to a VS installer project. I've heard too many stories about how it behaves oddly. I just browse to the darn file and add it.
Phil Wilson -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Peter Ritchie Sent: Thursday, May 11, 2006 7:28 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] Confusing Installer Project Is this DLL one that you are compiling? If you're not, I suggest making the DLL a member of the project for which the Setup project is for, then mark that DLL as "Content". Then, make sure the Setup project includes "Content" from your application project. This is not only handy from the setup project point of view (e.g., if I add content to the application project the setup project automatically picks it up without having to modify the setup project); but, is nice and tidy in terms of dependencies and source control. If you are building the DLL as well, make sure you have one solution with the application, the DLL project and the setup project and include the primary output from the application AND the DLL. On Thu, 11 May 2006 19:33:46 +1000, Peter Suter <[EMAIL PROTECTED]> wrote: >How is one supposed to create an installer that works ... >After creating the installer project about 3 months ago and lots of >enhancements and rebuilds later. >I came back today and deleted the old .msi, deleted the exe from the >installer and added it back, checking that the Source Path for one specific >dll was correct. Checked there was only one such dll, made sure it was >included in the output, uninstalled prior version, double-checked for prior >copies of the drive. >Then I rebuilt the installer. >After running the installer and checking on that one specific dll I >mentioned, I was very confused, surprised and somewhat annoyed to >discover that the dll that it had delivered was 3 months old. >And yes, I have just repeated this for the 3rd time. > >So, apart from creating a brand new installer project (every time?) >that I want to rebuild it with a new version, is there any way to get >this type of >project to give a nice, reliable, dependable - hey it is an installer, isn't >that exactly what I should be able to expect - output? =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
