[WiX-users] WiX v3.9 released

WiX v3.9 released Friday, October 31, 2014 The production/stable release of WiX v3.9 has been released. You can download it from here . Read more about the release at Rob's blog

Re: [WiX-users] Compression Level

Based on the following document (and probably other pots to the forum, long ago) I had implemented cab reuse. http://wixtoolset.org/documentation/manual/v3/howtos/general/optimizing_builds.html The cause of the problem detailed in this thread is that I had defined a single cab cache path without c

Re: [WiX-users] Burn doesn't warn if package names collide

On 10/31/2014 11:55 AM, Rob Mensching wrote: > Could you file a bug to say that there should be an error message too? Done: http://wixtoolset.org/issues/4574/ . -- Bruce -- __

Re: [WiX-users] Fwd: Wix Toolset 3.8 - Not removing from GAC on uninstall - Help!

The MSI/Fusion interface is very sensitive to the assembly description. If the attributes that end up in the MsiAssemblyName table don't exactly match the actual assembly then it won't uninstall. --- Phil Wilson On Fri, Oct 31, 2014 at 8:32 AM, Darrell Tunnell wrote: > So the logs lo

Re: [WiX-users] Compression Level

I did a little more research into this observation (that using -dcl:none and -dcl:high (or low, or no switch) all produces the exact same size output files (msi and related external cab files)). Since these experments were in part prompted by reading Bob's blog and the dev's discussions (http://ww

Re: [WiX-users] Burn doesn't warn if package names collide

Could you file a bug to say that there should be an error message too? _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Bruce Cran [mailto:br...@cran.org.uk] Sent: Friday, O

Re: [WiX-users] Burn doesn't warn if package names collide

Yup, that's what I did - I could also have changed source or destination filenames. -- Bruce On 10/31/2014 11:28 AM, Hoover, Jacob wrote: > A possible workaround would be to provide a MsiPackage/@Name putting them in > different directories in the layout. Ie: > > >

Re: [WiX-users] Burn doesn't warn if package names collide

A possible workaround would be to provide a MsiPackage/@Name putting them in different directories in the layout. Ie: ... Though I could see this as being a valid feature request to emit a warning. -Original Message- From: Bruce Cran [mailto:br...@cra

Re: [WiX-users] perMachine optional shortcut creation...

Correct but Windows Installer sill treats that like a user folder, which is the root of the requirement for an per-user key path. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message-

Re: [WiX-users] Burn doesn't warn if package names collide

On 10/31/2014 12:11 AM, Rob Mensching wrote: > Just so I'm sure I follow exactly, can you provide snippet of example code > that demonstrates the issue? -- Bruce --

Re: [WiX-users] perMachine optional shortcut creation...

According to http://msdn.microsoft.com/en-us/library/aa368276(v=vs.85).aspx "The installer sets the *DesktopFolder* property to the full path of the current user's Desktop folder. If an "All Users" profile exists and the *ALLUSERS* p

Re: [WiX-users] Fwd: Wix Toolset 3.8 - Not removing from GAC on uninstall - Help!

So the logs look good then? Would the logs show if the call to AssemblyUnpublish failed to remove it for any reason? Because I am starting with a clean slate every time i.e I'm using gacutil to ensure it isn't present in the gac, then run the install and verify that gacutil.exe /l crmado shows its

Re: [WiX-users] perMachine optional shortcut creation...

You're not wrong. It's just the way the Windows Installer handles multiple users logging into the same machine with Active Directory. It feels antiquated but it is how the Windows Installer works. _ Short replies here. Complete answers

[WiX-users] burn upgrades...

Am I missing something here? I have installed my product with version 14.8.6.x. Each build the GUID is changed, i.e.: The UpgradeCode is not changed, i.e.: “” The bundle.wxs has: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/burn-upgrades-tp7597628.html Sent from the wix-users m

Re: [WiX-users] Fwd: Wix Toolset 3.8 - Not removing from GAC on uninstall - Help!

>From log: Action 15:44:19: MsiUnpublishAssemblies. Unpublishing assembly information MSI (s) (E4:38) [15:44:19:981]: Executing op: AssemblyUnpublish(,,AssemblyType=1,,AssemblyName=CrmAdo,version="1.2.5.0",culture="neutral",publicKeyToken="BA966C247EE8FD34",processorArchitecture="MSIL",Descriptor=

Re: [WiX-users] perMachine optional shortcut creation...

What is the name of the alluser desktopfolder then?, when I do this, I wrap it into an directory-element, which contains an component, and then the shortcut, and the shortcut it self goes to the alluser desktop because perMachine is set. If the registryvalue which is required for removing it, is th

Re: [WiX-users] perMachine optional shortcut creation...

I believe there are several complaints about it, because if one admin installs the package, another could uninstall it and leave those entries stranded in the other users hive. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/ICE57-with-HKMU-td5795201.html -Original Message--

[WiX-users] Fwd: Wix Toolset 3.8 - Not removing from GAC on uninstall - Help!

Hello, I am new to WIX, and I am using the wix toolset visual studio extension (3.8). I created a new Wix "Setup Project" I added a reference from the Wix setup project to another project within my solution "CrmAdo" All i want to do is on installation, install the CrmAdo.dll to the GAC and then

Re: [WiX-users] perMachine optional shortcut creation...

DesktopFolder is a per-user location. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Phill Hogland [mailto:phogl...@rimage.com] Sent: Friday, October 31, 2014 7:53 AM To:

Re: [WiX-users] perMachine optional shortcut creation...

No. It smells wrong but that is what you need to do for a per-machine installation. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/perMachine-optional-shortcut-creation-tp7597616p7597621.html Sent from the wix-users mailing list archive at Nabble

Re: [WiX-users] Ways to Initiate Self-Repair in MSI

When a file association is created, and the app is installed properly, in the case of the Open verb, when a user double clicks on a file with that extension, the shell launches the registered application and opens the file. If the file association is advertised, and the application is not installe

Re: [WiX-users] perMachine optional shortcut creation...

But for perMachine installation, isn't HKCU wrong?, it kinda works though. On Fri, Oct 31, 2014 at 3:37 PM, Phill Hogland wrote: > I use something like this (without the condition, but that could be added, > in > which case I would also make the component transitive): > > >Direct

Re: [WiX-users] perMachine optional shortcut creation...

I use something like this (without the condition, but that could be added, in which case I would also make the component transitive): http://schemas.microsoft.com/wix/2006/wi"; /> -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.n

Re: [WiX-users] Auto-Updater

In your Bundle.wxa, do you have your in place? I wouldn't have copied the generated files. Easiest way to do a one off WixStdBA mod that I found was to use Z:\$(VersionMajorMinor)\wix3\build\ship\x86\ $(WixToolPath)Wix.targets $(WixToolPath)wixtasks.dll $(WixToolPath) In

[WiX-users] perMachine optional shortcut creation...

I have this working but I don't like my solution. I have a perMachine install in which I ALWAY need to create 1 shortcut. Optionally, I need to create a 2nd shortcut on the desktop (all users). My component definitions look something like this...Is there a better way to do this?

Re: [WiX-users] Auto-Updater

Hi Jacob, thanks for the links. So, i cloned your repo. After a lot of fiddling, I was able to compile wixstdba. Then I copied the generated files to the installation folder of the 3.9 RC: * BootstrapperCore.dll * ManageBundleRunner.dll * WixStdBA.dll I wanted to compile more, but there are s

[WiX-users] How to delete database while uninstalling from add/remove programs-WIX installation

Hi, I have created a WIX installer project and able to build and install with create database and IIS everything works fine. But while try to uninstall the application from add/remove program it is not removing the IIS web site, Application pool and SQL Database. Please guide me to delete t

[WiX-users] some dlls are missing while publishing

Hi, I created one installer for web application using harvesting method. installer gets created successfully and I installed it. It created directory and app pool without any error. but while running website I got to know some dll files are missing but those files are actually in solution file