Thanks for reply.
The problematic case is when standard MSI FilesInUse check will
detect the application but the user will answer Ignore. In such case
another FilesInUse dialog will not be correct.
Thanks anyway...
Stefan
Wilson, Phil wrote:
But if you're calling it from a custom action,
Hi. Please tell me how can i change the working
directory in my project to the one where I install the
files. I want to take the files from the place where I
install them directly. Instead of:
Property Id='SQLITE'C:\Program
Files\Sqlite\SQLite3.exe/Property
CustomAction Id=ExecuteSQLite
Hi...
The cached copy of MSI file is stored in hidden system folder
%WINDIR%\Installer\.
In this filder there are several files with .msi extension. You need
to find the file that belongs to your (broken) product and edit it
(via ORCA). You should back up the file you are about to modify in
case
I'm working on a project which have both a debug build and a release
build, and our goal is to make a MSI-package for both of them.
Normally this is not a big problem, but in our case the files used in
debug does not have the same name as in the release build.
Is it possible to solve this in a
Hi ,...
I am using preprocessor variables for the same purpose.
In the begining of my wxs file there is definition of variables:
?ifdef RELEASE ?
?define DebugReleaseDir=Release ?
?else ?
?define DebugReleaseDir=Debug ?
?endif ?
The file is compiled with command line
candle.exe
Thanks. I appreciate the code
snippet. It saved me some time.
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Friedrich,
Oliver
Sent: Monday, October 23, 2006 2:17 AM
To: Reggie Burnett; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Checking for .NET 2.0
Controls Winmexp m key Features a use is load
quickly dragdrop copy paste inverse am fit Zoom desktop Shade Snap Vcdvideocd
Supported plays operate system.Mere natural instincts or Spirit am build or
yourselves holy or pray Gods wait mercy of life merciful snatch in fearhating
clothing
Thanks for your insight. I am using 2.0.4415 as well. I may try managing the file versions as David suggested below.
-Tina
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of SimonBurgessSent: Saturday, October 21, 2006 6:13 AMTo: 'david adams';
Sorry for prompting about this issue again. I can see the feature
request is assigned to nobody and I am just wondering if I can have this fixed
soon since we will be releasing our final setup. Can I simply bump up the
priority of the feature request so it will be assigned soon?
Thanks,
Title: QuietExec error
Can anyone give me some advice where I could schedule these custom actions, I
need them to run after 2 local users have been created in the same installer,
Ive tried a few places including After = ConfigureUsers
but the error I get from the quiet execution suggests
Title: QuietExec error
Hey all,
Anyone using Votive3? I uninstalled my previous build,
downloaded and installed the new build... and it looks like Visual Studio is
still using the old build (I did follow the instructions... no visual studio
running, installed the project aggregator first).
I have a 3.9 gigabyte sized file. I didn't create this file and I am not
allowed to change it. But It doesn't go into a cab because a 2.0 gigabyte
limit (not enforced, but will FTU). Is there a way it cut the file into
pieces in wix? The problem is I don't want to have to have the user
Hi,
I'm trying to use WIX to create an installer for installing
a .hxs help file into the Visual Studio 2005 help system.
I tried this:
1. Created a merge module called 'HelpInstall.msm' using the
Help Integration Wizard project from the VS2005 SDK.
2. Used an existing Sample.wxs
Title: QuietExec error
Everything's fine for me (I'm using
3.0.2218.0)
Try uninstalling, making sure there's no
Windows Installer XML v3 directory (delete it if it
still exists) then reinstall again.
Anthony
From: Rob MacFadyenSent: Tuesday,
October 24, 2006 10:05 AMTo:
Magus,
PC Magazine used to have a utility called Slice32 which would slice a file up into specific sized pieces (originated in the floppy-disk era). It would create a custom splice.exe which would reconstitute the file. Not sure of the size limitations but you might get away with using this and
Doh!
The problem is that there is no Votive.xxx.zip for 3.0.2211.0 (though one
exists for 3.0.2015.0, 3.0.1821.0, and 3.0.1703.0)... so I went with the
2015 build.
From the website:
Download Core Toolset 3.0 means Wix-3.0.#.0-binaries.zip
Download ClickThrough 3.0 means ? unclear ?
Download
Title: QuietExec error
Hi all,
When I try to open a Votive solution (from previous 3.0
release) using the 2211 build I get the following message:
The project file must be opened in the Visual Studio IDE
and converted to the latest version before it can be built by MSBuild.
17 matches
Mail list logo