Re: [WiX-users] Preventing msi file from being directly executed by a user?

I agree, things like that work better if you get the application involved. The main thing that prevents the application getting involved is developers who believe it's entirely the install's issue to address and don't want to do the coding work. You might see recommendations to use a launch

[WiX-users] CompilerExtension xsd

I have a compiler extension which I wrote some time ago, based on studing the DifxAppExtension and other Wix Extensions. My new elements are children of wix:Component so I originally defined my xsd like this: ?xml version=1.0 encoding=utf-8? xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;

Re: [WiX-users] How to add references to other project in my WiX project programaticly?

You posted to the correct forum. I don't know anything about 'C# custom template wizard'. Sometimes my questions have also gone unanswered, but I appreciate the help when it is available. If you search the wix source code, filtering for just .cs files, there are about 22 hits on use

Re: [WiX-users] CompilerExtension xsd

I found the problem in my ParseElement implementation. Thanks. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/CompilerExtension-xsd-tp7598978p7598981.html Sent from the wix-users mailing list archive at Nabble.com.

Re: [WiX-users] How to add references to other project in my WiX project programaticly?

If you need an urgent answer, contact FireGiant (for $$$). Otherwise, this is a community mailing list. You'll get an answer when and if someone has the time to read the message, knows the answer, etc. You barely waited a day. -- Nicolás 2015-01-23 15:39 GMT-03:00 Igor Furman

Re: [WiX-users] CompilerExtension xsd

Actually the change to my ParseElement code did not resolve the problem and introduced other xsd validation problems. I reverted back to xsd which does not include the xs:appinfo/xse:parent. I can see in the Wix Extensions that xse:parent is used to declare multiple possible parents, which is

[WiX-users] Doesn't the Bootstrapper check to see if another instance of itself is running?

Hi, Just a quick question. Doesn't the Bootstrapper verify that it is not running another instance of itself? i.e. Launch your Installer (Bootstrapper) launch same installer again, two instances are now running... Steve -- View this message in context:

Re: [WiX-users] Adding an extension attribute, like bal:Overridable, but myext:Attribute

Look at the CompilerExtension code in wix\ that processes User element. It probably doesn't support extension attributes today. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message-

[WiX-users] Adding an extension attribute, like bal:Overridable, but myext:Attribute

Is it possible in my Compiler extension to add an attribute to an existing wix element, like the bal:Overridable attribute was added? I created a xsd and added to my extension, which adds my new attribute to the util:User element. While I did not implement the underlying parsing code or the CA

Re: [WiX-users] Doesn't the Bootstrapper check to see if another instance of itself is running?

Do you mean Burn? If so, I've never seen it do that before. Note: Windows Installer will do the same thing. Launch an MSI twice, you should get two UIs running. _ Short replies here. Complete answers over there:

Re: [WiX-users] How to distinct between Windows 7 and Windows Server 2008?

http://robmensching.com/blog/posts/2008/11/3/how-to-determine-if-you-are-installing-on-windows-client/ -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-distinct-between-Windows-7-and-Windows-Server-2008-tp7598975p7598976.html Sent from the

Re: [WiX-users] Doesn't the Bootstrapper check to see if another instance of itself is running? [P]

Classification: Public I thought two MSI's running at same time is a no/no? Steve -Original Message- From: Rob Mensching [mailto:r...@firegiant.com] Sent: January-23-15 6:00 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] Doesn't the Bootstrapper check to see if

Re: [WiX-users] Doesn't the Bootstrapper check to see if another instance of itself is running? [P]

Once an MSI enters the InstallValidate (InstallInitialize) action in the InstallExecuteSequence it will obtain a system-wide MSI lock. It will only release it once it finishes the InstallFinalize action. So, the short answer is generally: two MSIs running the InstallExecuteSequence at the same

Re: [WiX-users] Doesn't the Bootstrapper check to see if another instance of itself is running? [P]

Christopher Painter actually explained it better (about 3 years ago) - http://community.flexerasoftware.com/archive/index.php?t-198832.html 1) One Execute Sequence per system 2) One UI Sequence per process On Jan 23, 2015, at 7:39 PM, Joel Budreau joel.budr...@gmail.com wrote: Once an MSI

[WiX-users] How to distinct between Windows 7 and Windows Server 2008?

I have programmed a bootstrapper application with WiX 3.9 which - among others - installs IIS Express (if needed) and then activates the IIS features via a MsiPackage. In my MsiPackage i have the follwing options for Windows 8: / Property Id=DismX64

Re: [WiX-users] Preventing msi file from being directly executed by a user?

On 1/22/2015 10:33 PM, sky wrote: I'm now using burn cumstom bootstrapper application, and in my custom ba there is a step for validating product key. But since my msi file is external to the bootstrapper, anyone can install msi file directly without entering a product key. How can I prevent