Re: [WiX-users] Publishing to GAC

> > > note that CONSOLESERVICEDIRECTORY is never actually created > > > > Make sure that the assembly is signed. > we are using strong naming but not code signing. same as in the wix3.0 > project. > > > surely we would see an entry in the log if there was a problem

Re: [WiX-users] Publishing to GAC

Did you set the Assembly attribute in the File element to ".net"? Also, as I recall, you need to create a separate directory for the GAC'd assembly. So you would have two elements for the assembly with different parent directories. One to actually install it to disk, the other one to install it

Re: [WiX-users] GAC File Update

The scheduling just depends on whether you want to perform a full uninstall/reinstall and whether or not you want rollback support. Scheduling after InstallInitialize does a full uninstall without rollback support - but others can correct me. The important thing is having the file version set. Als

Re: [WiX-users] GAC File Update

Also, take a look at http://support.microsoft.com/kb/905238 If the assembly version remains the same, but the assembly file version changes, you will need to schedule RemoveExistingProducts after InstallIntialize Jacques On Wed, Apr 6, 2011 at 2:51 AM, David Watson wrote: > If you are followin

Re: [WiX-users] Registry Search in x86 installers doesn't work properly on x64 machines

I believe you need to issue two different installers and set the Win64 attribute for each RegistrySearch element. You should not specify the Wow3264Node in the path. If you need to do this in a single installer, you will need to condition the search so that it only triggers for the appropriate OS

Re: [WiX-users] MSBuild batching - Disabling incremental clean of MSIs only

now myself. I'm wondering if there is a bug in > here somewhere. I'll let you know if I find anything interesting. > > On Mon, Feb 21, 2011 at 3:59 PM, Jacques Eloff wrote: > > > Hi > > > > I rely on batching to generate multiple sets of MSIs from the same

[WiX-users] MSBuild batching - Disabling incremental clean of MSIs only

Hi I rely on batching to generate multiple sets of MSIs from the same wixproj files. The files are generated to the same output location, but are different based on properities I pass to the wixproj files that control thigns like the MSI name, etc. I'd typically invoke the project as follows Wi

[WiX-users] How to author a type 50 custom action that targets a binary stream

Hi I'm trying to author a custom action that executes a command and uses a file that's carried as a binary stream as input to the command. Basically, I want my MSI to just execute a custom action on this file. It won't install anything physically to disk. I keep running into ICE03 - "Not a valid

Re: [WiX-users] MsiGetProductInfoFromScript returns 1603

WHERE "Property"="ProductCode" > > I don't think you want ::MsiGetProductInfoFromScript(). > > On Thu, Jul 22, 2010 at 4:42 PM, Jacques Eloff wrote: > > > Hi > > > > I'm trying to extract the Product code from an MSI using C# (thi

[WiX-users] MsiGetProductInfoFromScript returns 1603

Hi I'm trying to extract the Product code from an MSI using C# (this is for a custom msbuild task I'm writing). I'm using the following definition for P/Invoke [DllImport("msi.dll", CharSet = CharSet.Unicode)] static extern Int32 MsiGetProductInfoFromScript(string scriptFile, StringBuilder pro

Re: [WiX-users] Signing of MSI / EXE + DLLs inside of MSI ?

If the DLLs go into the GAC then they must be signed. Jacques On Thu, Jun 3, 2010 at 10:04 AM, Pally Sandher wrote: > Sign your MSI to make the UAC prompts look prettier. > > Palbinder Sandher > Software Deployment & IT Administrator > T: +44 (0) 141 945 8500 > F: +44 (0) 141 945 8501 > > http:/

Re: [WiX-users] NetFxExtension and .NET 4

No, but you can easily code the logic in your installer. Also, Wix 3.0 does not work when installing .NET 4 assemblies to the GAC or trying to NGEN them, so it might be worth moving to 3.5 Jacques On Tue, Apr 27, 2010 at 11:06 AM, Alex Ivanoff wrote: > It requires WiX 3.5. Any support in 3.0? >

Re: [WiX-users] XmlConfig results in ICE27 failure

Almost. I added a non-empty file element. But, I believe this was fixed in Wix 3.5.1602 so that you don't need to add a dummy element. Jacques On Mon, Apr 5, 2010 at 12:33 PM, doglin82 wrote: > > so you are saying > > you did the following > > > Directory="INSTALLLOCATION"> > > > -

Re: [WiX-users] XmlConfig results in ICE27 failure

Filed as 2972975. Thanks, Jacques On Thu, Mar 18, 2010 at 6:20 PM, Bob Arnson wrote: > On 3/18/2010 8:28 PM, Jacques Eloff wrote: > > When I tried to build the project, I received the following error: > > Error 2 ICE27: Action: 'DuplicateFiles' in InstallExecuteSeque

[WiX-users] XmlConfig results in ICE27 failure

Hi I'm using Wix v3.5.1512.0. I've been playing with XmlConfig to modify the root web.config file, but ran into a strange issue today. I originally had the following in a component: When I tried to build the project, I received the following error: Error 2

Re: [WiX-users] How to execute a custom action that depends on an assembly being installed to the GAC

-bit registry entries to locate the file. Having multiple installers is not an option, so that takes using XmlFile elements out of the solution for me. Jacques On Fri, Mar 12, 2010 at 8:57 AM, Bob Arnson wrote: > On 3/11/2010 11:02 PM, Jacques Eloff wrote: > > I'v

[WiX-users] How to execute a custom action that depends on an assembly being installed to the GAC

Hi I have an installer that GACs a number of assemblies. Once this is done, I need to run a C# custom action (currently, this is an EXE). The problem is that this CA depends on one of the assemblies that was installed to the GAC earlier. The custom action modifies a file on disk. I know having man

Re: [WiX-users] SetupBld - quiet install defaults to passive install

Failed to CreateSetup. Also, I haven't setup NANT yet, so I'm just trying to get the project to build in VS2008 Thanks, Jacques On Thu, Mar 4, 2010 at 3:46 PM, Jacques Eloff wrote: > Hi > > I create a chained installer using SetupBld using a commandline like the > one belo

[WiX-users] SetupBld - quiet install defaults to passive install

Hi I create a chained installer using SetupBld using a commandline like the one below setupbld.exe -mi MSI1.msi -mi MSI2.msi -mi MSI3 -title "Foo" -setup obj\chained\tempsrc\setup.exe -license docs\EULA.rtf -out MySetup.exe When I launch the exe using /quiet, I still get a progress bar and the i

[WiX-users] Wix 3.5 - current state of Burn

Hi What is the current state of Burn (I'm running 3.5.1419.0) ? I'm looking to produce a bootstrapper fairly urgently that could perform the following: - Embed three MSIs - Run silently - Only install specific MSIs based on a set of launch conditions that are not in the MSIs themselves, but handl

[WiX-users] Installing .NET 4 assemblies into the GAC using WiX 2

Hi I just ran into a problem. I created an MSI that contains two assemblies. Assembly 1 targets .NET 3.5. Assembly 2 targets .NET 4. Both assemblies are delay signed. When I build the MSI using WiX 2, I noticed that the MsiAssemblyName table contains all the information for Assembly 1 (fileVersion

[WiX-users] How to get consistent behavior from ARPxxxx properties

Hi I never set any of the ARPxxx properties in my installer code. I noticed that by default, the entry for my application under HKLM\Microsoft\Windows\CurrentVersion\Uninstall\{guid} always contains an entry for NoModify set to 0x0001. On Vista and W2K8 I get both Repair/Remove options in ARP

Re: [WiX-users] Shared components

X, Y, & Z, none of those six keys > is part of MyDLL's component. Only things that always, in all > circumstances, > have to be installed together or not at all should be in the same component > together. > > -----Original Message- > From: Jacques Eloff [mailto:repst.

[WiX-users] Shared components

Hi I have a DLL that is installed by two MSIs. If I mark it as shared, I noticed that removing one product still leaves the DLL on the system. However, the components create different registry keys along with the DLL. So I would have the following: MSI 1, Component: MyDLL, Registry keys: A, B, C

Re: [WiX-users] Detecting if WiX 3.0 is installed

I would think doing a RegistrySearch on HKLM\Software\Microsoft\Windows Installer XML\3.0 should work. Assign to a property and use it as a launch condition. Jacques On Wed, Jun 24, 2009 at 3:03 PM, John Robbins wrote: > Hello, > > WiX 3.0 uses a Product Id="*" to autogenerate a product ID. Say

Re: [WiX-users] Registry entries not created on W2K8

Brian Rogers > "Intelligence removes complexity." - Me > http://icumove.spaces.live.com > > > On Tue, Jun 23, 2009 at 4:44 PM, Jacques Eloff wrote: > > > Hi > > > > I have an installer that was created using WiX 3.0.5217. > > > > W

[WiX-users] Registry entries not created on W2K8

Hi I have an installer that was created using WiX 3.0.5217. When I run the installer on Vista/XP/Win7, everything works. When I run it on W2K8, everything seems fine, ARP contains entries, etc, but none of the registry keys were created. I've compared a verbose log generated on Vista and W2K8 by

Re: [WiX-users] Trying to execute an exe file duringoraftermyinstall

ed. So if I understand correctly, all Custom Actions > must be in between the InstallInitialize action and the InstallFinalize > action in the InstallExecuteSequence? > > > -Original Message- > From: Jacques Eloff [mailto:repst...@gmail.com] > Sent: Tuesday, June 16, 2009

Re: [WiX-users] Trying to execute an exe file duringoraftermyinstall

Finalize action in the InstallExecuteSequence table > D:\Documents and Settings\gzsrcg\My Documents\Visual Studio > 2008\Projects\NFTSSetupA\NFTSSetupA\main.wxs30671 > NFTSInstaller > > -Original Message- > From: Jacques Eloff [mailto:repst...@gmail.com] > Sent:

Re: [WiX-users] Trying to execute an exe file during oraftermyinstall

r saying > unresolved reference to symbol 'CustomAction:Start_NFTS_Listener' in > section 'Product:*' I don't know which way to go at this point. All I > want to do is execute an exe file that was written in-house. > > Thanks, > Jim > > > -Original Message- > Fro

Re: [WiX-users] Trying to execute an exe file during or aftermyinstall

reading on a post in the archives on the net about the > wixca.wixlib having to be included or have a reference to it? > > > > -Original Message- > From: Jacques Eloff [mailto:repst...@gmail.com] > Sent: Monday, June 15, 2009 2:38 PM > To: General discussion for Windows

Re: [WiX-users] Trying to execute an exe file during or after myinstall

> > ...above the line that you mentioned, but something seems to be missing. > > -Original Message- > From: Jacques Eloff [mailto:repst...@gmail.com] > Sent: Friday, June 12, 2009 6:14 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users]

Re: [WiX-users] Trying to execute an exe file during or after my install

Hi Jim You still need to schedule the action. For example, Jacques On Fri, Jun 12, 2009 at 2:15 PM, MacDiarmid, James D < james.macdiar...@eds.com> wrote: > > I added the following code in my install with the intention that it > would execute the exe file at some point, but it's not working

Re: [WiX-users] Referencing variables inside wxl files

sn't even reference the .wxl files. > > Jacques Eloff wrote: > > Hi > > > > Is it possible to refer to variables inside your .wxl file? > > > > I have a situation where a value is defined inside an environment > variable > > that is used throughou

[WiX-users] Referencing variables inside wxl files

Hi Is it possible to refer to variables inside your .wxl file? I have a situation where a value is defined inside an environment variable that is used throughout various parts of a project (msbuild, custom cmd scripts and WiX). This value is passed to candle using the -d commandline switch, so it

Re: [WiX-users] Registry Settings Not Created

Hi Tina Not sure, but shouldn't the elements have a parent to create the key? So you would have something like I think that RegistryValue only sets the value of an existing key, it won't create the key if it does not already exist. Jacques On Tue, May 19, 2009 at 7:04 AM, Tina Basinger w

Re: [WiX-users] Rolling back after a major upgrade - is this possible

going back to previous version. > What you may or may not want in this case is uninstallable patch. > > Alex > > > > -Original Message- > From: Jacques Eloff [mailto:repst...@gmail.com] > Sent: Saturday, May 16, 2009 10:13 AM > To: wix-users@lists.sourceforge.

[WiX-users] Rolling back after a major upgrade - is this possible

Hi Let's say I have have two MSIs, one for v1.0 and one for v2.0 of my product. I install v1.0. Next, I install v2.0, replacing all the existing files and removing v1.0, assuming that I've used in v2.0 My question is this. What happens when I uninstall v2.0? Everything I've read seems to indica

[WiX-users] How to calculate MinVersion

Hi I'm aware that using MinVersion only inside a File element requires that it's one less than the actual value if one only uses that and don't rely on the language attribute. Let's assume there's a file with a version of 4.5.3.2. If I want to check for a min version of 5.0.0.0, should I set this

[WiX-users] Setupbld - bitmap option seems to be ignored (WiX 3.0.5217.0)

Hi I'm using setupbld and the default stub (setup.exe). When I run the command using the -bitmap switch, the dialog in the EXE that displays the license has a large option piece of real estate on the left. Is this where the bitmap is intended to go? I've tried using the bitmaps that's part of the

[WiX-users] WiX 3.05217.0 - Setupbld returns 0x80070005

Hi Solved the problem. After the first error (0x80070013) it copied the stub EXE and retained the read-only permission on the EXE I specified in my -output switch. I still had my output EXE with the read-only permission in my output directory when I reran the command after changing the permissions

[WiX-users] WiX 3.05217.0 - Setupbld returns 0x80070005

Hi I've been trying to build a bootstrapper using setupbld, but keep getting a result of 0x80070005 with a message that just states "Failed to CreateSetup". Initially I received 0x80070013, but that went away after removing the read-only property from setup.exe stub. My command has the following s