[WiX-users] Package download failed in Web Installer

Hi, I have created two msi file (SampleSetup1 SampleSetup2) using wix toolset3.8. In Installation,SampleSetup1 download successfully,but While downloading a SampleSetup2,it shown below error. (Note:Two msi were download successfully in another machine.) Error 0x80072ee2: Failed while reading

Re: [WiX-users] Adding Registry Entries in both 32 and 64 Bits

Thanks for your answer John. I am trying something similar in my bootstrapper code. This is what I wrote: ?if $(var.Platform) = x64 ? MsiPackage Id=MainPackage SourceFile=bin\x64\$(var.Configuration)\Installer.msi Vital=yes DisplayInternalUI=no / ?else? MsiPackage

Re: [WiX-users] Package download failed in Web Installer

What's the difference between the two machines? Firewall? Different network configuration/subnet? On Fri, Nov 7, 2014 at 7:15 AM, Mohamed Yasir yasirmohame...@gmail.com wrote: Hi, I have created two msi file (SampleSetup1 SampleSetup2) using wix toolset3.8. In Installation,SampleSetup1

Re: [WiX-users] Adding Registry Entries in both 32 and 64 Bits

No. Has to with the way WOW and the Windows Installer Service was implemented. It's not Wix-specific at all. At run time, the VersiontNT64 Burn variable is only defined on 64-bit OS's and you can use this to choose which MSI's to run out of a chain. -- John Merryweather Cooper Senior

[WiX-users] FireDaemon and WiX?

We are using FireDaemon for hosting services, instead of writing our own services. When using the OEM versioin, we need to do all the install ourself, and that we want to automate during the installation of rest of the software, but it seems like we cannot use the normal way using ServiceInstall

[WiX-users] [SPAM] Re: FireDaemon and WiX?

The wix elements use the msi standard tables for things like installing services and registry entries. This provides a better user experience, including rollback support, in contrast to calling an open ended external process like myservice.exe --install. Most of the information needed is in the

[WiX-users] Localizing Managed BA

Hi, I am trying to support localization for my Managed BA. I generated pseudo localized satellite assembly for en-US. Modified bundle.wxs to include satellite resource dll Payload SourceFile=..\Translation\lib\Release\en-US\Agilent.OpenLAB.Installation.resources.dll

[WiX-users] [SPAM] Re: Adding Registry Entries in both 32 and 64 Bits

I also deploy both x86 and x64 packages in my bundle. To clarify the use of preprocessor statements in your code snippet would cause the pre-compiler to include only one of the two code fragments at compile time. Probably not what you want. You can create two separate MSI projects for you

Re: [WiX-users] Localizing Managed BA

I think you should be putting the en-US satellite assembly in an en-US subfolder (Payload Name=en-US\Agilent...). This is a .NET thing, not Burn: http://msdn.microsoft.com/en-us/library/21a15yht.aspx On Fri, Nov 7, 2014 at 5:15 PM, gowri.malas...@agilent.com wrote: Hi, I am trying to support

[WiX-users] [SPAM] Re: Localizing Managed BA

I also wanted to comment that ILSpy along with ProcessMon and ProcessExplorer were helpful in sorting these issues out. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Localizing-Managed-BA-tp7597813p7597817.html Sent from the wix-users mailing

[WiX-users] [SPAM] Re: Localizing Managed BA

I had similar challenges back when I first created a mba and added localization about a year ago. I was just learning C# (from a C++ background) and so I was pretty green (and still am with C#). One issue that I had was that since my mba.dll is hosted in another application, there seemed to be a

[WiX-users] [SPAM] Re: Package download failed in Web Installer

I sometimes see errors like this when the bundle downloads several packages successfully and starts installing those packages. Then while downloading a later package, one of the earlier packages encounters an error, and starts a rollback. The download process is aborted resulting in errors like

Re: [WiX-users] How to suppress the StdBA Bootstrapper UI

Ahh!! That is really in detail and most helpful. Thank you very much for the helpful links and in details. Regards, Sampat -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-suppress-the-StdBA-Bootstrapper-UI-tp7597705p7597819.html Sent from

[WiX-users] Pop up a modify setup DialogBox

Hi All, I write a bootstrapper application and use “WixStandardBootstrapperApplication” GUI. After my bootstrapper application runs a MSI to install device drivers by calling a custom action dll , it indicates that installation successfully. But after a few seconds, it pops up another