Re: [WiX-users] Conditional Property, should be simple

are pre-processor statements and are evaluated at compile & build time. Properties are a runtime concept. You can use a element to achieve what you want (which is Wix shorthand for a set-property custom .action) -Original Message- From: Musa Biralo [mailto:musa.bir...@gmail.com] Sent:

Re: [WiX-users] WiX-users Digest, Vol 71, Issue 20

Do you want your installer to support silent installation? ( All installers should. ) If so, realie that the UI sequence doesn't get run during a silent install therefore your call to the second MSI will never happen. From: "Vivek Soni" Sent: Monday

Re: [WiX-users] WiX-users Digest, Vol 71, Issue 20

Hello all, Now I am able to launch any file (.exe, .msi) through checkbox in custom dialog.The current behavior is "when user click on checkbox the file is launched" but I want to launch it after completion of installation. Here is the code: NOT Installed I tried after chan

Re: [WiX-users] Distributing a C++ library

http://wix.tramontana.co.hu/ Palbinder Sandher Software Platform Engineer T:+44 (0) 141 945 8500 F:+44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the ** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Buil

Re: [WiX-users] WiX-users Digest, Vol 71, Issue 20

Sounds suspiciously like Concurrent Installations -> http://msdn.microsoft.com/en-us/library/windows/desktop/aa368010.aspx which even Microsoft warn against doing -> http://msdn.microsoft.com/enus/library/windows/desktop/bb204770.aspx#concurrent_installs (yes I did just copy & paste the above f

[WiX-users] Modifying MSIs from the bootstrapper

Hi all, I would like to provide my bootstrapper with functionality to modify the MSIs chained in the bundle after the first fresh installation. The problem is that once the MSIs are installed, the bootstrapper detects them and doesn't run them again. I took the setup in the wiX 3.6 sources as the

Re: [WiX-users] Installing VS2010 support

One may want to take a look at HKLM\System\CurrentControlSet\Control\Session Manager\DOS Devices. Adding a proper entry there creates a SUBST like drive that should be system wide not just for the user. Once you create the entry, reboot for it to be applied. I would assume Rob's comment on the SU

[WiX-users] Condition under component is not working

Hi, I added condition for IIS version under component but it is not working. Please anyone help for this problem. Thanks, Sujitha -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...

Re: [WiX-users] Condition under component is not working

Level Conditions apply to Features. Remove the Level attribute. -- John Merryweather Cooper Build & Install Engineer - ESA Jack Henry & Associates, Inc.(r) Shawnee Mission, KS 66227 Office: 913-341-3434 x791011 jocoo...@jackhenry.com www.jackhenry.com -Original Message- From: Sujit

Re: [WiX-users] Modifying MSIs from the bootstrapper

Modify keeps the current states of the MSIs. You need to return a different requested state from OnPlanPackageBegin to cause the MSI to installed/repaired/uninstalled. On Mon, Apr 16, 2012 at 7:23 AM, burn baby burn wrote: > Hi all, > > I would like to provide my bootstrapper with functionality to

Re: [WiX-users] Condition under component is not working

"#7" is a string. What string are you comparing it too? I don't think I've used a string comparisons with any greater or less than before. On Mon, Apr 16, 2012 at 8:33 AM, Sujitha Ramamoorthy < sujitha.ramamoor...@aspiresys.com> wrote: > Hi, > > I added condition for IIS version under component b

[WiX-users] Burn: ExePackage display name

Where does the description displayed above the status bar come from for an ExePackage? The help implies the Provides element can be used but this doesn't seem to be valid in the schema. Thanks Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com -

[WiX-users] WixStdBA Foundation

Should WixStandardBootstrapperApplication.Foundation work? I couldn't get this work, among the issues I had to specify LicenseUrl or LicenseFile which shouldn't be required and even with these it still failed to load the theme when I ran it. Neil Neil Sleightholm X2 Systems Limited n...@x2syst

Re: [WiX-users] Bug in Candle NAnt Task Define element

Thanks, Rob, for informing me that these NAnt tasks are going to be deprecated. I'll stick to using the task from here on out. On Sat, Apr 14, 2012 at 12:25 AM, Rob Mensching wrote: > Sounds like a bug. I don't think many people use the NAnt tasks and we are > looking at removing them in future

Re: [WiX-users] Escaping brackets [ ] in merge modules (MSM)

I'm not sure what you mean by that. " Merge Modules append the Module/@Id to all identifiers." Which identifiers? How is that breaking the escape characters? Could you please elaborate? Thanks in advance Erkan Celme Phone: 312-927-5180 -Original Message- From: Rob Mensching [mailto:r.

Re: [WiX-users] Escaping brackets [ ] in merge modules (MSM)

I'm guessing that you are declaring a property in a merge module and trying to use it in the installer. The merge module will append a .GUID to the property name unless you give it set the SuppressModularization attribute. Alternatively you can use the correct property name including .GUID in

[WiX-users] MSP question

Hi everyone, I'm using pyro to attempt to generate an .MSP file to use. In its .wxs, I have (for now) a single componentref which seems to work out ok, i.e. the patch successfully installs the additional file referenced by the new component. However, for some reason, the .MSP also as part of it

Re: [WiX-users] Condition under component is not working

Even if I remove level attribute condition is not working. -Original Message- From: John Cooper [mailto:jocoo...@jackhenry.com] Sent: Monday, April 16, 2012 9:22 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Condition under component is not working

[WiX-users] Loose file support in Burn?

I am creating a bootstrapper app using Burn. One of the MSI package has loose file (i.e. files outside of CAB or MSI so they can be changed after MSI has been created). The MSI installer itself works just fine with the loose files. However, when I bundled the MSI inside a chain and changed the l

Re: [WiX-users] Condition under component is not working

Even if I compare IISMAJORVERSION with number it is not working. -Original Message- From: Rob Mensching [mailto:r...@robmensching.com] Sent: Monday, April 16, 2012 9:30 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Condition under component i

Re: [WiX-users] Loose file support in Burn?

It should just work. Can you provide specific details about how you laid out your MSI? The Burn log file is also usually helpful. Ideally, open a bug and attach an example project that does not contain any private information in it. On Mon, Apr 16, 2012 at 8:50 PM, Zhichao Hong wrote: > I am cre

Re: [WiX-users] Condition under component is not working

Take a look at a verbose log file and see if the Properties equal what you think they equal. On Mon, Apr 16, 2012 at 8:55 PM, Sujitha Ramamoorthy < sujitha.ramamoor...@aspiresys.com> wrote: > Even if I compare IISMAJORVERSION with number it is not working. > > > > > Description="$(var.Enterp

Re: [WiX-users] Loose file support in Burn?

Rob, I have created a solution using VS2010 Pro and Wix 3.6 RC0. The main MSI package is called DemoSoftware. It will install a file called ReadMe.txt with content "original" text in it. The installation is per machine (ProgramFiles (x86)) on windows 7. The DemoBA project is the bootstrapper a

[WiX-users] Question about Bootstrapper entry in the control panel ARP

I am using Wix 3.6 RC0 release. Created a bootstrapper application with one MSI embedded. I did not give the bootstrapper a name so it will not show up in the ARP list. The embedded MSI has a name and an entry in the control panel. When I manually uninstall the MSI itself, and then run the boot