Thank you, I started messing around with the source code and found that
QuitExec seems to be unmanaged code, and therefore was starting to think
what you confirmed.
As I explained previously I have the code up and running using a CA with
ExeCommand(both config files are installed):
CustomAction I
Well, seems like $(Configuration) is set by Votive, but
inside the WiX-code I can not access it?
With :
I get the Errormessage:
Error 1 Ill-formed preprocessor
variable 'Configuration'. Variables must have a prefix (like 'var.',
'env.', or 'sys.') and a name at least 1 character long.
I am currently using v3.0.1703.0 a bit old in the tooth now but have not
had time to use any later.
Peter
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 07 November 2006 03:34
To: Dyson, Peter
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Com LocalSer
Hi,
I'm trying to harvest website info using the following command:
heat website DefaultWebSite -out c:\testje2.wxs
I'm getting the error:
heat.exe : error HEAT0001 : The directory cannot report the number of properties
.
Exception Type: System.NotSupportedException
Stack Trace:
at System.
Oliver,
I'm still a bit unsure about where you are getting the
error (I.e. are you building the installation from the command line? Within
Visual Studio 2005? Somewhere else?). Unfortunately, I also don't use Votive so
the vast majority of this reply is guesswork!
I suspect that the MSBui
Lerudjordet, Morten Minge wrote:
> As I explained previously I have the code up and running using a CA with
> ExeCommand(both config files are installed):
> CustomAction Id="XMLParser" BinaryKey="XmlPreprocess" Impersonate="yes"
>
Yes, MSI supports running an executable from the Binary table.
Dyson, Peter wrote:
> I am currently using v3.0.1703.0 a bit old in the tooth now but have not
> had time to use any later.
>
I'm not sure exactly when the change was made, but the current version
uses [#] syntax. BTW, if you use WiX v3, you should consider taking
drops more often. As v3 is s
Thanks again, that did it. Looked at the code and did not see a reason
for why wixca.dll from V2 would not work in my code.
After renaming both the file id and the name of wixca.dll to CAwix.dll
everything went as planed.
So for other struggeling with using CAQuietExec this is how to do it.
Did
Yep, Oliver summed it up pretty well. As far as Votive is
concerned, you can define the preprocessor variable by entering “Configuration=$(Configuration)”
on the compiler property page (not linker property page). Also, make sure to
put the parenthesis (which you missed in your example below
I have a case where my merge modules need to tell if they are running in an upgrade, or a fresh install. I have a property that is getting set in my main install to indicate that an upgrade is occurring. I thought that I could then just use that property in my merge modules to condition actions t
I’m trying to put a check box on my license agreement
dialog using the following:
Re: [WiX-users] CheckBox question...
Just a guess, but I’d try changing the CheckBoxValue=”1” to a “0”
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
Lovett
Sent: Tuesday, November 07, 2006 10:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CheckBox question...
I’m
trying to
Chris:
Set your property to no value by default
For an unchecked box, I believe that the Property @Value is empty. Checking
the checkbox sets it to the value defined in the control.
David Adams
MSN MessengerID: [EMAIL PROTECTED]
>From: Cullen Waters <[EMAIL PROTECTED]>
>To: Chris Lovett
Tina:Take a look at the IgnoreModularization tag. You define it in the merge module wxs file.()Dana
On 11/7/06, Tina Basinger <[EMAIL PROTECTED]> wrote:
I have a case where my merge modules need to tell if they are running in an upgrade, or a fresh install. I have a property that is getting set i
That worked, thanks. I guess I was confused by the following warning:
C:\MQ\ndp\fx\src\xmltools\Tools\XmlNotepad\Wix\XmlNotepad.wxs(112,0): Warning
CNDL1006: Property 'LicenceAccepted' does not contain a Value attribute and is
not marked as Admin, Secure, or Hidden. The Property element is bei
Are you distributing this merge module to anyone else who
isn't using WiX? If not, it may be a lot easier to convert from a Module to a
Fragment and simply link it into the main installer.
light can accept any number of .wixobj and .wixlib files on
the command line. The only restriction is
Which version of WiX are you using? What operating system is this problem
occurring on? Which version(s) of the .NET Framework do you have installed?
Technical detail: get_Count will throw a NotSupportedException if the
underlying ADSI object doesn't implement the IADsPropertyList interface. The
d
Hi,
I am using WiX to create my msi package. I just moved to building with Wix 3.0 and I hit the exception
"error LGHT0204 : ICE39: PID_WORDCOUNT value in Summary Information Stream is not valid. Source image flags must be 0, 1, 2, or 3." during linking.
Changing the InstallPrivileges="limit
Hi,
I have a Win32 service that should be installed with my MSI.
The typical WIX entry for a service would look something like:
Name="MyService"
DisplayName="My Service Name"
Description="My Service Descrip
Microsoft has never documented how the shared service
hosting through SvcHost.exe works, so it's pretty much only MS who can create
such a service. The Type can be set to "shareProcess", but I think this is still
meant for installing your own EXE which hosts multiple services, rather than a
Also, one of the restrictions on svchost.exe is that
you can't name it as an authorized application to get through the Windows
firewall, just to give you a heads up in case you might want to do that.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
DimmickS
Dear all,
I ran into a problem when I try to run the msp file. I followed the
steps in the Wix tutorial to generate a msp patch for a msi package.
If I use command line to install the patch, it works fine. However, if
I simply double click on the msp file, the "Modify" , "Repar" and
"Remove" UI co
Hi, In our project we have daily builds. For daily buils we are NOT changing the product ID,package ID and upgrade ID. So when user tries to install latest build, it will give repair option, which will re-install the package. This is working fine, as long as no new files are added to the MSI
Hi,...
The package code of your MSI should change every build. That's why
the GUID ---- exist in WiX.
You should read this:
http://windowssdk.msdn.microsoft.com/en-us/library/aa370579.aspx
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/set
Hello,
I am trying to pass a property to a method in a DLL. But I
am not getting the actual property value in my DLL through MsiGetProperty.
It returns the length of parameter as zero. But still method
returns successfully.
Can you tell me exactly which string from WXS file should I p
I've just started to use Wix v3 (or any .msi based installer toolkit for
that matter)
so please bear with me.
First question: How would I add a "line edit" control to a dialog?
I have found examples for PushButtons, RadioButtons, static text etc but
nothing that looks like something that might
I have a third party product with an msi based installer that I need to
install
alongside my own stuff.
Simply launching msiexec from a custom action does not seem to work as
msiexec will complain that another installer (presumably my own) is already
running.
Decompiling the third party instal
27 matches
Mail list logo
