[WiX-users] Post Event Resources from Microsoft: Configuring Outbound Access and Publishing Web Servers with ISA 2004 Virtual Lab

Dear Kamil, Connect with TechNet

Re: [WiX-users] suppress the progress indicator

Just run your msi with: msiexec.exe /i YOUR_MSI_PACKAGE.msi /q This will run absolutely silent without any UI. Stefan Don Tasanasanta wrote: > I’ve created a very basic wix install to install one file. This msi is > to run as quickly and quietly as possible. > > > > Is there a way to turn of

[WiX-users] suppress the progress indicator

I’ve created a very basic wix install to install one file. This msi is to run as quickly and quietly as possible.   Is there a way to turn off the progress indicator during install? I do not have a ui sequence in my code but the progress indicator still shows.   __

[WiX-users] big agouti

stocck coverage highlighting booming markets Fellow Inveestor, big news are hitting on thursday for AG AO!!! Somebody knows something...place AG AO on the radar!!! Get ready for a volatile 2nd half of 2006 - one where the Bulls and Bears will BOTH be proved wrong. But odds are, we'll see anothe

Re: [WiX-users] The property name that I set on the command line becomes all upper cased

Public properties (which can be set from the command line) are (and should be) be all UPPER CASE. If you reference or use the not-all-upper-case properties, you cannot set such properties from the command line.   Take a look at the topic in MSDN for details.   http://msdn.microsoft.com

Re: [WiX-users] The property name that I set on the command line becomes all upper cased

I don't believe you can do that.  MSI allows only public properties to be set via the command line.  And a public property is one that is defined to be all upper case.  Check the MSI documentation for more details on private, public, and public secure properties.Jason Swager"dangle123 ..." <[EMAIL

Re: [WiX-users] The property name that I set on the command line becomes all upper cased

I’m surprised that Windows Installer was nice enough to uppercase it for you and didn’t just display an error.  You cannot specify a mixed-case property on the command line.  Only uppercase properties can be specified because they are public properties.  This is due to the security design f

Re: [WiX-users] My Installer Requirements

It does have to do with WiX. WiX is what generates the MSI database. MsiInstallProduct() is an API function that you can call from a program to install an MSI database. In fact, that is, among other things, exactly what msiexec.exe does. Internally it calls MsiInstallProduct to install the MSI y

[WiX-users] The property name that I set on the command line becomes all upper cased

When I try to set a property throught the command line as follows, the name received as upper case by the MSI. msiexec.exe /i sample.msi /l*v c:\sample.log PropertyName="SomeValue" PropertyName becomes PROPERTYNAME as indicated in the log.   Is there a way to prevent the property name from changing

Re: [WiX-users] Silent install messing up my custom action

Yes, my custom action is sequenced in the Execute Sequence. It is sequenced after launchconditions which is sequenced after appsearch in the execute sequence.   From what I can tell from the logs cost finalize sets up the directory properties and assigns them to the components so if I se

Re: [WiX-users] My Installer Requirements

Magus wrote: > Interesting how that doesn't seem to have anything to do with wix. I have no idea how to write a program for MSI But that's *exactly* what WiX does. If you are writing WiX code you are generating an MSI database. WiX just gives you an easier (and in my opinion) better way to do so

Re: [WiX-users] My Installer Requirements

Interesting how that doesn't seem to have anything to do with wix. I have no idea how to write a program for MSI, I've tried finding tutorials, but I have been unsuccessful. I am not an SQL guy either, I don't know how are when to use MsiSetExternalUI(), exect that its not something I can call fro

Re: [WiX-users] My Installer Requirements

There are external UIs that can "skin" a MSI file.  From what I understand, the skinning application/engine builds an EXE that contains the MSI file.  The EXE is a boot-strapper of sorts that executes the MSI file, but hooks in its own UI.  You can find one at http://www.skincrafter.com/installer.h

Re: [WiX-users] My Installer Requirements

For requirement 1, it seems your best bet may be to make a small wizard application that displays the Welcome/Splash screen and the combined license agreement. At the end of the wizard, your MSI is run with MsiInstallProduct(). The MSI would then have the other dialogs such as feature selection t

Re: [WiX-users] Silent install messing up my custom action

Don:Is your custom action sequenced between both the and the tags?  If it's not in the InstallExecuteSequence table, it will not run on a silent install. DanaOn 8/15/06, Don Tasanasanta <[EMAIL PROTECTED]> wrote: I have a custom action that changes the location of the installation di