Appreciate the responses, they did get me thinking along different lines.
The problem turned out to be from a merge module, where had reused that same dll. While the dll in the merge module and the one in the main installer had the same version they were 3 months apart. Windows Installer decided on the older one. So, problem solved (sort-of) The Installers seem to be riddled to an outstanding degree. I havn't used Project Output since the time a web installer decided that "project output" included all my source code. I became exceptionally cautious about testing each installer build - multiple times it built the approx correctly sized msi, the output was a small fraction of the required dll's. And, since I just discovered that some key files cause the Installer to refuse to build, I'm now shopping for a half decent one. regards ps ----- Original Message ----- From: "Vince P" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Thursday, May 11, 2006 7:35 PM Subject: Re: [ADVANCED-DOTNET] Confusing Installer Project Installer packages can be a bit tricky if you really don't take time to read the docs about them , becaue IMHO a lot of it is not intuitive. When you create a Project, right click on the project, choose Add | Project Output from the context menu and select whichever project represents your program's external face (either the exe or primary dll if there is such a thing) In the properties of the Setup Project, anytime you want to do rebuild with your new updated code, change the Version number. A dialog box will ask if you want to update the Project Code, allow it to do so. When you rebuild the setup project your new MSI file will have the knoweldge that it's an update to an older version and will handle that situation if installed ona computer with an older version. --- Vince
-----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Peter Suter Sent: Thursday, May 11, 2006 4:34 AM To: [email protected] Subject: [ADVANCED-DOTNET] Confusing Installer Project 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? flame on! =================================== This list is hosted by DevelopMentor® 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 =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
