Re: [WiX-users] ModuleInstallExecuteSequence not being merged into msi

2008-03-25 Thread Geoff Finger
That was in fact the problem, thanks! On Sat, Mar 22, 2008 at 11:42 AM, Bob Arnson [EMAIL PROTECTED] wrote: Geoff Finger wrote: In the ModuleInstallExecuteSequence table of the msm files we have rows such as: Action: RemoveOldDriver.B391C18A_6953_11D4_82CB_00D0B72E1DB9 Sequence

[WiX-users] Changing an installation in Add/Remove fails if msi is missing

2008-03-25 Thread Geoff Finger
If we run our installation and then delete the msi when we're done, uninstalling the program through add/remove works but selecting the Change option fails. First it pops up the The feature you are trying to use is on a network resource that is unavailable dialog, and if we cancel out of that it

[WiX-users] SetTargetPath causes errors in remote installations. Is there an alternative?

2008-03-21 Thread Geoff Finger
Our installation needs to install SQLExpress under certain conditions, and unfortunately we don't know what those condtions are until the user has already gotten through the installation, so we can't run it ahead of time through the setup.exe. After much experimentation I got an ExeCommand custom

[WiX-users] ModuleInstallExecuteSequence not being merged into msi

2008-03-19 Thread Geoff Finger
I'm having some trouble getting a couple of 3rd party msm files to work correctly. The original instructions said that along with including the merge module we should also schedule several custom actions in the msi. After that failed I looked around the archives and found several threads saying

[WiX-users] Accessing directories above SourceDir

2008-03-11 Thread Geoff Finger
We have two Projects, A and B. There is a file in ProjectB that needs to be run by ProjectA. Originally thinking that ProjectB was a child of ProjectA I wrote some code that included the lines: CustomAction Id=ResetProjectBDir Property=PROJECTBDIR Value=[SourceDir]\PROJECTBDIR / CustomAction

Re: [WiX-users] Adding an ok/cancel popup dialog?

2008-03-05 Thread Geoff Finger
Okay, thanks. I added an extra page after the Welcome dialog with the confirm/cancel message. Just one more page for the users to click through I guess :) On Sat, Mar 1, 2008 at 2:47 PM, Bob Arnson [EMAIL PROTECTED] wrote: Geoff Finger wrote: I hooked up the dialog to the Next button

[WiX-users] Adding an ok/cancel popup dialog?

2008-02-26 Thread Geoff Finger
We just recently added the Upgrade Id value to the installer and the testers have complained that it deletes the old version of the program without asking first, so I'm trying to add an ok/cancel popup dialog at the first step of the installer if a previous version is detected to warn them about

Re: [WiX-users] Failing gracefully from ServiceControl?

2008-02-25 Thread Geoff Finger
be pretty easy to accomplish with custom action type 34 scheduled after InstallFinalize and with ExeCommand set to: net start servicename Alex -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Friday, February 22, 2008 3:42 PM

Re: [WiX-users] Failing gracefully from ServiceControl?

2008-02-22 Thread Geoff Finger
be an issue. Geoff Finger-2 wrote: I've got several services I'm trying to install. If I add Start='install' to the ServiceControl element then it will try to start them, but it will almost always fail with a 1920 error. I'm pretty sure this is because some of the services

[WiX-users] Failing gracefully from ServiceControl?

2008-02-21 Thread Geoff Finger
I've got several services I'm trying to install. If I add Start='install' to the ServiceControl element then it will try to start them, but it will almost always fail with a 1920 error. I'm pretty sure this is because some of the services are dependent on side-by-side assemblies that are being

[WiX-users] Checking for .NET version/existance

2008-02-18 Thread Geoff Finger
The program I'm installing has an Interop we'd like to install on systems using .NET, but we still want to be able to install the program with reduced functionality on systems without .NET. However when we tried installing it on such a system we got an error because it tried to add the interop to

Re: [WiX-users] Checking for .NET version/existance

2008-02-18 Thread Geoff Finger
Whoops, it turns out that it was actually being installed twice in different spots, once I updated _both_ spots to use the check everything was fine. That's what i get for trying to debug stuff at 6pm without making sure i've checked all 5000 or so lines of code =P (And perhaps I ought to pull

Re: [WiX-users] Multi-file assembly problem

2007-12-07 Thread Geoff Finger
PROTECTED] wrote: Have you tried putting them in separate components or just using the CopyFile element? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Thursday, December 06, 2007 6:16 PM Cc: wix-users@lists.sourceforge.net

[WiX-users] Multi-file assembly problem

2007-12-06 Thread Geoff Finger
Short version: Is there any way to override what seems to be the default behavior and force Wix/msi to install additional file elements in an assembly Component into the WinSxS folder even though they aren't included in the main file's manifest? Or alternately are there any kind and generous souls

Re: [WiX-users] Multi-file assembly problem

2007-12-06 Thread Geoff Finger
. This is why people have so many problems with COM in-process servers that try to load DLL dependencies from their application directory. Geoff Finger [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/06/2007 03:38 PM To wix-users@lists.sourceforge.net cc Subject [WiX-users] Multi

Re: [WiX-users] Multi-file assembly problem

2007-12-06 Thread Geoff Finger
the files in the same folder though - I'd be curious to see what GetModuleFileName returns on those modules. Kelly Geoff Finger [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/06/2007 04:29 PM To wix-users@lists.sourceforge.net, [EMAIL PROTECTED] cc Subject Re: [WiX-users] Multi

Re: [WiX-users] Uninstalling WinSxS in Vista

2007-11-06 Thread Geoff Finger
On Nov 5, 2007 9:33 PM, Bob Arnson [EMAIL PROTECTED] wrote: Geoff Finger wrote: I've run into an issue with Vista where the side by side assemblies installed to WinSxS do not get removed when the uninstaller is run. Known issue and I'm not aware of a workaround. And yes it sucks. Well

[WiX-users] Uninstalling WinSxS in Vista

2007-11-05 Thread Geoff Finger
I've run into an issue with Vista where the side by side assemblies installed to WinSxS do not get removed when the uninstaller is run. I found the a href=https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=260142;Microsoft Connect Issue 260142/a which seems to

Re: [WiX-users] x64 and ProgramFilesFolder vs. ProgramFiles64Folder

2007-11-02 Thread Geoff Finger
On Oct 24, 2007 7:59 AM, Bob Arnson [EMAIL PROTECTED] wrote: Geoff Finger wrote: Instead what I found was a post claiming I don't think you want to reference ProgramFiles64Folder either. Use ProgramFilesFolder and Windows Installer will put things in the correct directory based upon

[WiX-users] x64 and ProgramFilesFolder vs. ProgramFiles64Folder

2007-10-23 Thread Geoff Finger
I have two installers for our project, one for 32 bit and one for 64 bit and I'm running into some problems with the x64 version. My first question, is there a tutorial for how to build x64 installers with wix 2.0 somewhere? I could have sworn I saw a link to one at some point, but I can't find

Re: [WiX-users] x64 and ProgramFilesFolder vs. ProgramFiles64Folder

2007-10-23 Thread Geoff Finger
After poking around a little more I've found something in the logs that might be related. There are a lot of messages about: WIN64DUALFOLDERS: Substitution in 'C:\Program Files (x86)\InstallDir\File.exe' folder had been blocked by the 1 mask argument (the folder pair's iSwapAttrib member = 0).

[WiX-users] Allowing sources from either x64 or x86

2007-05-22 Thread Geoff Finger
I've got a rather simple question that is probably due to some obvious in hindsight error, but I'm totally stymied by it and haven't had any luck searching for a solution. I just recently switched from an x86 machine to an x64 machine running XP x64. I suddenly find that some of the installers

Re: [WiX-users] Allowing sources from either x64 or x86

2007-05-22 Thread Geoff Finger
PROTECTED] On Behalf Of Geoff Finger Sent: 22 May 2007 23:23 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Allowing sources from either x64 or x86 I've got a rather simple question that is probably due to some obvious in hindsight error, but I'm totally stymied by it and haven't had any

[WiX-users] InstallLevel has no effect when modifying an installation

2007-04-25 Thread Geoff Finger
My projects has three options in the Setup dialog. Typical with InstallLevel 3, Admin with InstallLevel 1, and the Custom option which takes it to the Custom Setup dialog with InstallLevel 3 as the default. This all works fine, but I've run into trouble trying to modify the installation by

Re: [WiX-users] Accessing the Source Directory

2007-03-23 Thread Geoff Finger
control over. On 3/22/07, Rob Mensching [EMAIL PROTECTED] wrote: Why are you copying files from the original media instead of just using the File element? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Thursday, March 22, 2007 3

[WiX-users] Accessing the Source Directory

2007-03-22 Thread Geoff Finger
I've been trying to figure out how to copy some files located in the directory the msi file is being run from to the Install directory, the big problem being that I couldn't find an easy way to fetch the value of the source directory. SourceDir leads to the root of the drive and CURRENTDIRECTORY

[WiX-users] Disabling a Feature

2007-03-16 Thread Geoff Finger
I have a feature that can only installed if .net 1.1 or higher is also installed. The description for the feature indicates this requirement but I don't want to trust to the users' good sense, some of them will either not read the message or ignore it and get into trouble. Searching through the

Re: [WiX-users] Using InstallShield msm files causes an error

2007-03-14 Thread Geoff Finger
] wrote: That should work. If you have any custom actions in your msm verify that the sequencing is after the cost standard actions. Thanks, Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: Wednesday, March 14, 2007 1:04 PM

[WiX-users] Sequential msi installations

2007-01-31 Thread Geoff Finger
The program I'm working on needs to have either SQL 2005 or the SQL Server Native Client installed. We've decided that if neither of those have been installed we should give the user the option of installing the Native Client after the basic installation is finished in order to simplify things for

Re: [WiX-users] Problem with CDATA and default values in Conditionstatements

2007-01-30 Thread Geoff Finger
Swapping in lt;gt; fixed both issues! Thank you! Why is it necessary to use that in some cases though when in other spots I used without any problem? Shouldn't using the CDATA wrapper have prevented it from being an issue? On 1/30/07, Albert van Peppen [EMAIL PROTECTED] wrote: Did you try

[WiX-users] Problem with CDATA and default values in Condition statements

2007-01-29 Thread Geoff Finger
I can't get the comparison to work in the CDATA statement for my Condition elements and trying to set a default value on the property that is being tested is breaking them as well. I have a radio button selection during the setup that determines whether the service that is being installed will

Re: [WiX-users] How to integarte an .cat file

2007-01-25 Thread Geoff Finger
I'm not sure what steps you've already completed so here's the entire process I followed. In my case I was using MS VS 2005, obviously some steps my have to be addapted depending on the enviroment you're working under. First you have to create a key if you don't have one already: makecert -n

[WiX-users] Installing shared assemblies

2006-10-27 Thread Geoff Finger
Thanks Mike for your earlier help with private assemblies. We've dropped the idea of doing anything special with them but as expected we've moved on to shared assemblies so I've got some more questions for anyone who can help. I've taken one of our old COM dlls and added an AssemblyInfo.cpp

Re: [WiX-users] Private Assemblies with Wix

2006-10-20 Thread Geoff Finger
On Fri, 20 Oct 2006, Mike Dimmick wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Finger Sent: 20 October 2006 00:54 To: wix-users@lists.sourceforge.net Subject: [WiX-users] Private Assemblies with Wix I hope this email gets

[WiX-users] Private Assemblies with Wix

2006-10-19 Thread Geoff Finger
I hope this email gets through (several earlier emails sent from my gmail account resulted in SMTP Error (state 9): 451-Could not complete sender verify callout) I've been working on the Wix installer for a project at my company for the past couple weeks, but the project manager has decided