I have a .NET application that runs on both x86 and x64. I'd like to have a
32 bit WiX installer (so it that will work on both platforms) but I'd like
it to install to /Program Files/ rather than /Program Files (x86)/ on 64 bit
operating systems.
How would you go about doing this?
My idea was to
Unfortunately MSI packages marked 32-bit simply cannot install files into a
64-bit directory, and a package marked 64-bit cannot be used at all on a
32-bit platform. And a package cannot be marked for both bitnesses.
It is a limitation of Windows Installer. You have to do two packages (one
for
What are you doing with HELPINSTALLERDIR? How are you consuming it?
-Original Message-
From: Jimmie Eriksson [mailto:eriksson.jim...@gmail.com]
Sent: Sunday, May 16, 2010 3:51 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch converts
Greetings,
I am using WIX 3.0, and working on WIX Tutorial 10 (
http://www.tramontana.co.hu/wix/lesson10.php ), and I have come up to a problem
in dealing with trying to fill a listbox.
I used the example provided and managed to create a FillListBox.dll using
Visual Studio 2008, but I had to
I Get the following error when I run WiXCop.exe to migrate from Wix 2.0 to
3.0
C:\Program Files\Windows Installer XML v3\binWixCop.exe -f sourcefile.wxs
-set1 wixcop.config
wixcop.exe : fatal error WXCP0001 : The URL cannot be empty.
Parameter name: url
Stack Trace:
at
My wixcop.config file contains:
?xml version=1.0 encoding=utf-8?
Settings
IgnoreErrors
Test Id=WhitespacePrecedingCDATAWrong /
Test Id=WhitespacePrecedingNodeWrong /
Test Id=WhitespaceFollowingCDATAWrong /
Test Id=WhitespacePrecedingEndElementWrong /
/IgnoreErrors
/Settings
Hi,
In my first msi there are four features. Based upon the selection of a
feature/features in the first msi, i have to copy files in my second msi.
How to catch the information of what feature(s) selected in the first msi?
Is there a way other than writing to a registry and read it from
Hi All, please help why such error is happened?
WriteIIS7ConfigChanges: Entering WriteIIS7ConfigChanges in
C:\Windows\Installer\MSI78A3.tmp, version 3.5.1714.0
WriteIIS7ConfigChanges: Error 0x800700b7: Failed to add defaultDocument
Files element
WriteIIS7ConfigChanges: Error 0x800700b7:
Hi Matt,
I've doublechecked Binares and Content output groups but without success. I run
heat from command line:
%WIX%\bin\heat project ..\..\src\Configurator.csproj -pog:Binaries
-pog:Content -out heat.wxs
The only reference I have in outputs is compiled assembly. Heat completely
ignores
Sounds very useful Tomasz. I was in the process of writing something very
similar last summer before a major release to for that release all subsequent
release installations. Up until that release we didn't require any version of
.NET, just the VC++ 2005 redistributable controls. As we now
Hi All,
I want to remove a registry value during Un-installation. Could someone
reply me what to do about it?
Thanks,
Thangaraj Natarajan
Analyst - GWIMT (Core Technologies Solutions)
--
This message w/attachments
There is one option while creating a key like
Action=createKeyAndRemoveKeyOnUninstall. This will delete the registry
entry while uninstalling.
Regards, Subramanyeswari
--
View this message in context:
This is similar to a number of bugs I recently fixed in the IIS Extension. It
looks like I may have missed one. I will take a look. I have opened bug
3002703 to track the issue.
Thanks!Eric
From: chilavegp...@mail.ru
To: wix-users@lists.sourceforge.net
Date: Mon, 17 May 2010 14:22:23
OK, thanks a lot. Also in 3.5.1714 I found the following - my msi creates 3
virtual dirs during installation and removes them during uninstallation.
Msi, built with 3.5.1710 uninstalls properly and removes 3 virtual dirs, but
msi built with 3.5.1714 uninstalls all virtual dirs (even, which were
This was actually a bug in the IIS custom actions. It should be fixed in the
latest build : 3.5.1714.00. Please give it a try.
-Eric
From: houssam.ham...@netiks.com
To: wix-users@lists.sourceforge.net
Date: Thu, 6 May 2010 12:03:46 +0300
Subject: Re: [WiX-users] IIS error during Repair
Hi all,
I struggle with writing a WiX installer that can conditionally install an
executable as Windows service. The executable can be run as Windows service
but it is not required to. The user should get an option to install the
service during setup or not. The option could be in form of a
Can you confirm your scenario:
Website exists with virtual dirs.
Your installer locates the site and installs virtual dirs with different paths.
On uninstall, all virtual dirs, regardless of path, are removed.
Do you think you could attach your repro source to the bug?
Thanks,
Eric
I think the usual solution is to add two components, both containing the file,
and one of the components installs it as a service, the two components having
mutually exclusive install conditions.
Phil Wilson
-Original Message-
From: Andreas Hirth [mailto:a.hi...@luratech.com]
Sent:
I would probably be doing two Components as you mention in your last
attempt. The ICE30 error is probably related to duplicate shortnames.
You can probably get around this by specifying your own shortnames
rather than having WiX generate them for you. It might be giving each
Component the same
I see, thanks, so basically all I have to do is to have an inmediate CA that
sets the RB property and this will be available if the deferred RB CA runs:
in terms of the scheduling, I am thinking of doing the below:
CustomAction Id=RB_QtExecDeferredExampleWithProperty_Cmd
Take a look at your solution level configuration options. My guess is that 'Any
CPU' is setup to only build C#/VB/etc projects. You probably have a 'Mixed
Platforms' configuration that also includes the WiX projects. My guess is that
the IDE is choosing 'Mixed Platforms' as the default while
I'm trying to understand wixlib. I've spent an hour searching do, web,
and archives.
After I create a wixlib, how do I include it in my installation?
Kurt Jensen
**
This email and any files transmitted with it are confidential
The PropertyGroup code is as follows:
PropertyGroup Condition= '$(Configuration)|$(Platform)' ==
'Release|x86'
OutputPathbin\$(Configuration)\/OutputPath
IntermediateOutputPathobj\$(Configuration)\/IntermediateOutputPath
DefineConstantsWiXProductName=BeamGage
I assume that you found the Adding WiX References topic in the WiX help:
http://wix.sourceforge.net/manual-wix3/votive_wix_references.htm
The only thing I would add to that is that you need to add a ref to the
fragments that you want to include in your main project. You could add
PropertyRef or
Yes, I have created a separate WixLib project and added a reference.
Now, how do I include the WixLib components so that I can reference them in the
Feature?
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Monday, May 17, 2010 4:50 PM
Maybe you can achieve what you want by retrieving one of the special folder
paths. MsiExt 1.2 has a new CA called Win32_GetSpecialFolderPath that wraps
SHGetSpecialFolder.
http://msiext.codeplex.com/releases/view/39468
dB. @ dblock.org
Moscow|Geneva|Seattle|New York
-Original
I haven't tested it, but I wonder if the whitespace is causing problems.
What happens if you try:
DefineConstantsWiXProductName=quot;BeamGage
Professionalquot;;WiXProductVersion=$(WiXVersion)/DefineConstants
Or:
DefineConstantsquot;WiXProductName=BeamGage
27 matches
Mail list logo
