Blair,
Thank you for your reply.
Now I think I've got the clear notion of GAC and SxS, and
how I should schedule RemoveExistingProducts.
And it's okay with the product-level versioning issues.
As for the component rules and the versioning rules of files,
I'll check them out in "TAO of Windows I
Looking at your situation, this is what looks to me to be your solution:
1- I'm assuming that your transformed heat outputs don't have any Directory
elements with an Id of either localized or neutral. Remove them if they
exist in your transform.
2- Under your Product element (or some other manuall
Yeah, this is more or less what I'm doing. The issue is that I still need
to define the directory structure somewhere. Zach suggests defining it
manually which is probably the best solution but unfortunately isn't really
an option for what I'm doing. What would be ideal is if light would handle
Inline...
-Original Message-
From: Kihara Nobuo [mailto:soft...@gmail.com]
Sent: Friday, January 08, 2010 6:43 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Major Upgrade, RemoveExistingProducts, Downgrade
Prevention and Component Guid
Hi all,
I'm new
Hi all,
I'm new to WiX and Windows Installer, just having walked through the
lessons of WiX Tutorial.
Now I'm wondering how I should plan the upgrading of the product.
These are my questions:
1) Am I right to say that generally the major upgrade would be the
best solution for relatively small pro
Assuming I understand what you're asking, I think the official support for this
is available only in MSI 4.5:
http://msdn.microsoft.com/en-us/library/bb736308(VS.85).aspx
Where does your PATCHFOUND property come from?
Phil Wilson
-Original Message-
From: Sandeep Kumar Bushnam (Wip
How about using XSLT to change the into
in the localized wixlib's wxs file from heat?
-Original Message-
From: Kyle Huey [mailto:ksh...@ufl.edu]
Sent: Friday, January 08, 2010 7:09 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using Heat multiple times => Duplicate symbols
Is UnInstallPatchFeatures in the patch or in the baseline MSI?
Unless you are using MSI 4.5 or later, nothing in the patch is visible when
the patch is removed (since the patch's view is completely removed).
If you are using MSI 4.5 or later, you can set the PatchUninstall='yes'
attribute on the
Hi Kyle,
What about using the XSLT to change the duplicate elements to
elements, and define the directory structure once, in
another file?
I do something like this when I first create a setup project--I do not use
HEAT dynamically at build time. I like to have the directory structure laid
out i
A component is a atomic unit of work in WIX. Any kind of files u want to
install, entries in the registry u wanna make, all go in a component.
Ya u can put ur xmlconifg element in a component, even though the file being
installed is a part of ur installation.
but i suggest u put it in a separate co
I still don't understand.
>From the main tutorial blog on Wix.
>http://www.tramontana.co.hu/wix/lesson1.php#1.1
"The component is the atomic unit of things to be installed". But the xml file
I am modifying is not a part of my install. It is already installed. So do I
still put it in a comp
How can this save testing? You're going to invent something like a custom
action to check various combinations of properties (and I don't know what that
would be) and you're not going to test it? You'd need to test that right-click
an MSI file and Repair does what you expect, that any repair en
Re posting the link.
http://wix.sourceforge.net/manual-wix3/util_xsd_xmlconfig.htm
On Fri, Jan 8, 2010 at 10:20 PM, ricky sundrani wrote:
>
> U'll have to use it under a component.
>
>
>
>
> ...
>
>
>
>
> See the link
> http://wix.sourceforge.net/manualwix3/util_xsd_xmlconfig.htm
>
> Here se
U'll have to use it under a component.
...
See the link
http://wix.sourceforge.net/manualwix3/util_xsd_xmlconfig.htm
Here see the parents of the XmlConfig element.
On Fri, Jan 8, 2010 at 8:08 PM, Kerber, Cameron
wrote:
> Well I don't see any file search element under Property. Also w
Hello all,
I am using heat to generate the source for two .wixlibs which are lighted
together with some other pieces to form my final MSI. Heat is used on two
different directories at build time. One of these directories holds all of
my language specific files "/localized/" and the other holds a
Well I don't see any file search element under Property. Also where do I put
the XML Config element. If I just put that element under the Product element
will it get executed?
Thanks
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: Fr
Have you tried setting the @File attribute of XMLConfig / XMLFile to a file
on the target system? You could create a Property with a FileSearch element
to find a file on the target system and then use this property as @File.
I'm not sure, haven't tried this yet J
Best regards,
Sebastian B
You can use the XmlConfig element to change any xml file.
You can use the attributes of XmlConfig element like
File:
Action:
On:
ElementPath:
Name :
Node
Sequence: < Sequence no of actions>
Here are some links which maybe useful:
http://stackoverflow.com/questions/1648221/deleteing-whole-se
So I've seen a lot of documentation in using the XML Util Extension to modify
xml files. But generally all those tutorials are for changing XML files that
are being included with the install.
How would I change an XML file that is already existing for where I am going to
deploy my Install? So
Awesome... this works. Thanks Kalev for the help.
- Original Message -
From: "Kalev Lember"
To:
Sent: Friday, January 08, 2010 4:56 PM
Subject: Re: [WiX-users] Showing actual MSI name on Windows UAC dialog
> On 01/08/2010 09:09 AM, Sudripta Nandy wrote:
>> Whenever I execute/run my
On 01/08/2010 09:09 AM, Sudripta Nandy wrote:
> Whenever I execute/run my MSI on Windows VISTA / Win 7, Windows shows a UAC
> message asking:
>
> 'Do you want to allow the following program to install software on the
> computer?"
>
> Program name:.msi
>
> Why does the program name specify some rand
The issue has got resolved by .def file & then specifying at
Linker/Input/ModuleDefinatioFile in project settings which seems mandatory
for release build.
Thanks for all the inputs.
Regards,
Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Friday, January 08, 2
One issue that I noticed with depends.exe is that in case of release version
DLL the exported functions are decorated like ?funcName@@y...@z but whereas
in case of debug version the function remained same(not decorated)
- Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.c
I am able to see the exported functions & the MSI if using
__declspec(dllexport) instead .def but still the issue exists with release
build not working while adding to .cub file
- Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Friday, January 08, 2010 4:57 AM
I am using #pragma comment(lib, "msi.lib") in the code
- Nag
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Friday, January 08, 2010 4:52 AM
To: 'Blair'; 'General discussion for Windows Installer XML toolset.';
'ra...@symphony.cc'
Subject: RE: [WiX-users] getting
While I checked the release version DLL with Microsoft depends.exe found
that the DLL does not listing the exported functions & msi.dll but whereas
the same is listed in the debug version DLL & hence no issues while I run
the debug version but the release version fails. What am I missing here?
- N
Hi,
I 'm creating a path using Purly WIX Patch approach . In that I have one custom
action which I'm executing on install and another on uninstall of the patch.
But while uninstalling the patch the second custom action is not called. Can
someone help me in fixing this issue.
On Patch Install I
27 matches
Mail list logo
