That's right. I my experience it doesn't really matter if component remains
transitive (my case) or loses transitive state when removing the patch. The
question to ask is: if patch application removed file(s), when patch itself is
removed how will those files come back? And the answer seems to b
Thank you for your answer. I may not understand your reply correctly
but I was looking for a way to keep a variable in one place for
various projects. In other words, currently I have product version
variable for future upgrade in wxs file but I need this information in
other parts of my code which
On 1/24/2010 1:18 PM, Cody Gibson wrote:
> Depth="1" AssignToProperty="yes">
>
The AppSearch action doesn't guarantee an order the table's rows are
processed, so you can't rely on being able to use the results of one
search in another. The log has the details:
> Action start 19:23:35: AppS
I did that (as demonstrated in my original post) but it didn't help. Any other
ideas?
Thanks,
Cody
From: Rob Mensching [...@robmensching.com]
Sent: Sunday, January 24, 2010 7:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [Wi
You need to make sure you have a reference to the VS90_ITEMTEMPLATES_DIR.
Unfortunately, the usage of the property (aka: using []) will not create a
reference. In this case, just add a
On Sun, Jan 24, 2010 at 10:18 AM, Cody Gibson wrote:
> Yes I'm sorry for the confusion. I guess I did write m
The MSI SDK provides a number of APIs to get at those pieces of data from a
custom action. The WiX toolset ships with many custom actions. You might
read through those to get an idea how to read MSI databases.
On Sun, Jan 24, 2010 at 3:47 PM, CP YEH wrote:
> I have Wix project that contains prod
I have Wix project that contains product codes and version information
and I would like to find a way to use these information from C++
project because I do not want to define these variables two different
places.
Could anyone tell me how to achieve this?
Thanks.
YEH
-
In addition, you can probably create your own self-extracting program
to take care of your needs. In other words, you just need to create a
simple C/C++ program to add your msi to it. So when the user executes
your exe, it would detach the msi from itself and call CreateProcess
to launch msiexec.
P
dotNetInstaller 1.8 has support for custom UI elements. It's not "awesome" or
"template-based", but it's a start. It lets you have custom controls outside of
mandatory ones like the list of applications.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Kevin
http://remoteinstall.codeplex.com has been very successful for us.
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original Message-
From: Jordan Fitzgibbon [mailto:jord...@microsoft.com]
Sent: Thursday, January 14, 2010 1:52 AM
To: General discussion for Windows Installer XML toolse
Yes I'm sorry for the confusion. I guess I did write my question backwards...
why does A (my work around) work when B (what I thought should be the right way
of doing it) does not work.
Specifically I'm asking about using the VS90_ITEMTEMPLATES_DIR property from
the WixVsExtension. I'm tyring t
As usual, forgive me for shameless advertising.
dotNetInstaller 1.8 was released today, January 24th, 2010. Here're some
highlights.
* Added support for uninstall sequences with new command-line /i and /x
switches, supportsinstall, supportsuninstall global options in configurations,
compone
Thanks all who have responded. I followed MikeR's comments and came up with
the following - I found that I had to reference the x64 Architecture
variable when defining both the Component and the ComponentRef within the
Feature section, as follows:
13 matches
Mail list logo
