I've been on this for a few hours now. I'm trying to write an upgrade. From
what I understand, it should be as simple as adding a MajorUpgrade section with
a DowngradeErrorMessage string, and having the same upgrade code. However, it
just isn't working out that way. I can install the old pro
That information is already in the log, typically in your %temp% folder.
But for the specific question on how to set a property using another
property, use the SetProperty element.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Property-Id-Value
Thank you for your time and comments. I am still digging through the verbose
log captured during the on-demand install. I am also re-reading the
sections in your book related to on-demand installs.
One brief clarification is that I run the wix bundle (with multiple msi
packages), which I compile
I have heat.exe from Wix 3.8.1128.0 (RTM) working well against many, many C++
projects using the VS2010 Toolset.
Running heat.exe from Wix 3.8 against C++ projects that have been upgraded to
the VS 2013 Toolset always gives the following error:
Error 53 Build error during harvesting: C:\
I want to print a message containing the value of a property that is set
in a Custom Action. I have the Custom Action setting the property. Now I
want to print that value in the WiX installer.
Say my Custom Action sets property "THESTRING" = "Hello world!"
I tried:
but that didn't work.
I s
It's not that you want to violate security, but that the situation
seems to be that now a limited user cannot create a HKLM key where
previously it apparently worked. My point about other users and HKCU
was that I couldn't tell if you were advertising a feature for the
same user or you were adverti
While this is a answer to changing a different file attribute
(File/@Keypath), you would need to do something similar.
http://stackoverflow.com/questions/8034798/wix-installer-using-xslt-with-heat-exe-to-update-attributes
--
View this message in context:
http://windows-installer-xml-wix-toolset
Also, it seems if I use 63 or more characters, *candle* complains and tells me:
c:\InstallerBuilder\TrainingMaterials\Training Materials-Materiels de Formation\
Wxs\TrainingMaterials-Training Materials-Materiels de Formation-20140414103809.w
xs(7) : error CNDL0032 : The Media/@Cabinet attribute's
It doesn't seem that spaces by themselves are a problem to produce an output -
only if the name is long. Spaces do produce ICE03 but the error doesn't seem to
be fatal.
Keith Douglas
Statistics Canada | 170 Tunney's Pasture Driveway, Ottawa ON K1A 0T6
Statistique Canada | 170, promenade Tunne
From:
http://www.installworld.com/index.php?view=article&catid=42%3Aice&id=233%3Aice03&option=com_content&Itemid=138
Bad cabinet syntax/name
Only Cabinet data type is allowed. The Cabinet data type must be used
in the Cabinet column of the Media table. If the cabinet name is
preceded by the
Hi,
I'am creating an Installer for an Apache Perl CGIi Project. Sometimes the
server files are edited by a User.
In this case the File is not overwritten. I Need to overwrite these files
during Installation process.
My File / Component List is automatically created by Heat.exe. Is there any Way
I have determined through some trial and error that I was running into length
limitations on the Cabinet attribute on the Media tag. I note that it only
seems to have come up when using light ; candle doesn't seem to care. In Wix
3.7 (we are slow moving on upgrades) this produces a
light.exe :
Hi I found it very easy to use publish wizard in visual studio to generate a
.zip package that can be imported in IIS once the Web deploy extension has been
installed. I believe an msi would always be the best solution for a customer so
is it possible to get WIX to install it for me by simply ex
Hi I found it very easy to use publish wizard in visual studio to generate a
.zip package that can be imported in IIS once the Web deploy extension has been
installed. I believe an msi would always be the best solution for a customer so
is it possible to get WIX to install it for me by simply ex
Hi All,
I have a set of shared 3-rd party DLLs ver.1
To deploy with other products I created:
1. Merge module version 1 Product Code A
2. Installer that includes just the merge module, Product Code B,
Upgrade Code C
The reason of such approach it was that for some products I cre
In your MSI you might want to look at the 'remember property' pattern. I
have found these posts helpful:
http://www.nichesoftware.co.nz/node/633
http://robmensching.com/blog/posts/2010/5/2/the-wix-toolsets-remember-property-pattern
I use the above pattern for properties which are passed to MSI pa
I got the solution for my first problem (files not removed from installed
location). I forgot to set the MSI property value on uninstallation. So the
MSI feature is not get called and files not removed. Now the files are
removed correctly.
Could anyone please share example/way for removing selecte
Hi,
I have a main installer which is around 200 mb, created a Patch which is
around 1 mb
When running the patch it takes around 8 minutes of out which
WriteRegistryValues is taking 5 minutes
Is there any way possible to reduce the time taken by WriteRegistryValues?
Thanks and Regards
Ravi Shank
I have the following properties in MSI.
1
1
0
0
0
I pass only the installtype from burn bootstrapper to the MSI. How do I
achieve the following in .wxs file ? and setup the property values in
runtime. Based on these property values, I install components. Note: I'm
using burn
19 matches
Mail list logo
