Re: [WiX-users] Too many CA:s (LGTH0179)

2011-04-06 Thread Asker Brodersen
te a custom table to list the files as input to the CAs. -Original Message- From: Asker Brodersen [mailto:asker.broder...@esri.se] Sent: 06 April 2011 13:04 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Too many CA:s (LGTH0179) The ESRIRegasm utility

Re: [WiX-users] Too many CA:s (LGTH0179)

2011-04-06 Thread Asker Brodersen
Re: [WiX-users] Too many CA:s (LGTH0179) What is special about your registration that means you can't just heat them, your code implies it's just regasm? -Original Message----- From: Asker Brodersen [mailto:asker.broder...@esri.se] Sent: 06 April 2011 06:41 To: WiX-users@lists.sour

[WiX-users] Too many CA:s (LGTH0179)

2011-04-05 Thread Asker Brodersen
Hi, During installation/uninstallation we need a special registration of our dll:s. This lead to four CA:s being scheduled for each dll: $Meldis.Search.dll>2 $Meldis.Search.dll>2 $Meldis.Search.dll=2 $Meldis.Search.dll=2 But as I have close to a hundred dll:s, this results in th

Re: [WiX-users] Cabinet does not contain any files

2009-12-06 Thread Asker Brodersen
Yes, Add in a in your wix project file and and SourceDir will look there! >From my project file: ..\BuildTools\WiX\3.0.5419.0\ $(WixToolPath)Wix.targets wixtasks.dll False ..\Build\Release $(DefineConstants);BuildVersion=$(Version);ProductDescription=$(Description) Regards, Aske

Re: [WiX-users] multiple entries in add remove programs.

2009-12-06 Thread Asker Brodersen
Giora, do your versions differ by more than the fourth digit? I have found that if you install 1.0.0.0 and then 1.0.0.1 they will both be listed as installed. Incrementing the third digit (ie 1.0.0.0 to 1.0.1.0) the older version will be replaced. To enable replacement also by fourth digit versi

Re: [WiX-users] Cannot register assembly

2009-11-30 Thread Asker Brodersen
) with those numbers (watch out for source control since the file has to be modified, you may want to copy the file and build the assembly with the copy and not the original). -Blair -Original Message- From: Asker Brodersen [mailto:asker.broder...@esri-sgroup.se] Sent: Sunday, Novembe

Re: [WiX-users] Cannot register assembly

2009-11-29 Thread Asker Brodersen
mat like "$(DefineConstants);version=$(BuildVersion)" based on how the version information is represented in your build's process flow. -Original Message- From: Asker Brodersen [mailto:asker.broder...@esri-sgroup.se] Sent: Thursday, November 26, 2009 11:35 PM To: General di

Re: [WiX-users] Cannot register assembly

2009-11-26 Thread Asker Brodersen
es where you supply those inputs to candle or the build environment, as appropriate. That would "automate" that part of the process without resorting to sed. How do you currently set your assemblies' versions today? -Original Message- From: Asker Brodersen [mailto:asker.brod

Re: [WiX-users] Cannot register assembly

2009-11-26 Thread Asker Brodersen
: [WiX-users] Cannot register assembly What kind of registration do you need? COM/interop registration? Or just the ability of the two assemblies to find each other when installed into the same directory? -Original Message- From: Asker Brodersen [mailto:asker.broder...@esri-sgroup.se] Sent

[WiX-users] Cannot register assembly

2009-11-26 Thread Asker Brodersen
Hi, I'm trying to have WIX register my assemblies, but when I do the install they are only copied to the right location, not registered. What's the correct way of doing this, I don't want them in the GAC? This is what I'm doing (two different attempts): Looking around the net I've see