Re: [WiX-users] VS11 and WixProj

Latest WiX release is not Beta. It's 2719. On Thu, Mar 22, 2012 at 11:23 AM, ShitalKumar Mehta (Synergy Technologies LLC) v-shm...@microsoft.com wrote: I suppose as per March 10 post from Rob, latest WIX Release [3.6 beta] has support for VS11. VS11, however wouldn't show templates for

Re: [WiX-users] Burn: cache only Burn engine?

If the user renames the executable, then the default prompt for the executable will be incorrect but he or she can still browse to it with the old name. On Wed, Mar 21, 2012 at 9:43 AM, Vadym Verba vve...@sdl.com wrote: Hello. Recently we have some problem with bundle maintaining. Here is use

Re: [WiX-users] Burn: uninstalling an MSI

Which BootstrapperApplication are you using? If you're using wixstdba, I expect it does not handle this scenario well. You'd want to create a BA that is designed to show the MSI UI instead of it's own UI. On Thu, Mar 22, 2012 at 9:17 AM, robert_y...@non.agilent.com wrote: Some further research

[WiX-users] Repairing ice64

Hi Folks: I'm currently writing the first of what could be many installers for a company. I have the following inside the TARGETDIR directory: Directory Id=ProgramMenuFolder Directory Id=COMPANYSTARTMENUFOLDER Name=Raised Bar Directory Id=ApplicationProgramsFolder Name=Surface

Re: [WiX-users] Burn: cache only Burn engine? Source prompt in BA

If the user renames the executable, then the default prompt for the executable will be incorrect but he or she can still browse to it with the old name. Thanks for pointing me to the right direction). For those who might have problems with source prompt in BA here is solution: 1) Subscribe on

Re: [WiX-users] Repairing ice64

Add a RemoveFolder to your start menu. RemoveFolder will only remove empty folders. Description Remove an empty folder if the parent component is selected for installation or removal. By default, the folder is the directory of the parent component. This can be overridden by specifying the

Re: [WiX-users] Burn: uninstalling an MSI

Thanks ! Yes, it's using the standard bootstrapper. In the meantime I hunted through the source and found MsiEngineCalculateInstallLevel, MsiEnginePlanAddPackage and WiuInitializeExternalUI.. wondering if there is a good way to intercept the UI level in a custom BA. Maybe using

[WiX-users] DTF question

Hi everyone, I'm wanting to write a little utility to help our deployments server monitor installations. I can use the Database class on an MSI and get its productcode with an appropriate query and hence then verify that it is installed. However, MSPs don't seem so straightforward. What's a

Re: [WiX-users] DTF question

1) Enumerate the installed Product Codes; 2) Select the one of interest; 3) Enumerate the patches installed to that ProductCode; 4) Check if the patch of interest is one of the installed patches to that ProductCode. Fast and dirty. I'm sure there are more elegant ways to get it. -- John

[WiX-users] harvesting an out of process com server

Hi: I'm adding an out of process com server to my installation that I'd normally register with /regserver on the command line. How would I go about adding the necessary entries to a wix installer-I know I can use heat to register an inproc com server. Any help appreciated. Regards Sean.

[WiX-users] using a 32-bit project in a 64-bit installer

Hi: I'm writing an installer in visual studio. I have a 32-bit com server that is written in atl. This com server does not have a 64-build configuration and therefore doesn't build when I build the 64-bit configurations. If I add the Project.TargetPath to my installer, what path will this