Thanks Nick. It worked for me !!
-Vishwajit
-Original Message-
From: Nick Ramirez [mailto:nickra...@hotmail.com]
Sent: Thursday, September 16, 2010 7:31 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to refer WIX properties within .wxs files
Oops.
Replace
The WixUI_InstallMode checks are there in the default wixui_mondo.wxs
file - all I've done is added the LEGACY_APPDATA check. Absolutely
nothing changes in the log between the first click and the second click,
it's all very strange! It only does it when the LEGACY_APPDATA check
fails (i.e.
Hi,
You can check out my sample code on this page:
http://madbutcher.dyndns.org/snippets/
Here you can find a SQL instance selector CA for WiX 2.0 but it still
works for WiX 3.6.
It has also some tricks to correctly detect 32 and 64 instances
correctly (in a tricky way)
Regards,
Albert van
Yes it is new, but I see it's potential ;-)
Here are the logs:
Content of stdux_20100920084141.log:
[0FDC:0E24][2010-09-20T08:41:41.562+01:00]: === Logging started:
2010-09-20T08:41:41+01:00 ===
[0FDC:0E24][2010-09-20T08:41:41.562+01:00]: Executable:
From WiXUI_Mondo.wxs
Publish Dialog=SetupTypeDlg Control=Back
Event=NewDialog Value=LicenseAgreementDlg1/Publish
Publish Dialog=SetupTypeDlg Control=TypicalButton
Event=NewDialog Value=VerifyReadyDlg1/Publish
Publish Dialog=SetupTypeDlg Control=CustomButton
You have a component rules violation. Windows Installer requires
different components to have entirely independent contents.
You have various options: some good, some bad.
A. Require release N-1 be removed entirely to install release N. A major
upgrade can do this automatically.
B. Rename the
No I was not dismissing your advice at all, just trying to understand
the problem more fully. I've changed it now as per your advice and now
it seems to work.
Thanks for your help.
Mark.
On 20/09/2010 10:55, Pally Sandher wrote:
From WiXUI_Mondo.wxs
Publish
Hi,
I am using the wix project to create a MSI.
In the directory tag I use the following entry
Directory Id=Solutions Name=Solutions LongName=Solutions
When I compile I get the following error
ERROR :FileName.wxs(1605) :
error CNDL0027 : The Directory/@Name attribute's value, 'Solutions', is
IIRC I had similar issues when attempting to create patches using the
Pyro method in WiX 3.0 hence I've stuck with the PatchWiz method. I'm
sure if I stuck at it I could probably work out what's going wrong when
I try using the Pyro method but since I have a method which works
there's not much
If youre using Wix 3 or greater, try deleting the LongName attribute.
-Original Message-
From: Karthic Sampthkumar [mailto:karthic_sampthku...@mindtree.com]
Sent: 20 September 2010 11:40
To: 'wix-users@lists.sourceforge.net'
Subject: [WiX-users] Reg: error CNDL0027
Hi,
I am using the
To answer Grant's query, the official recommended method is that you
need to use separate x86 x64 packages. Windows Installer won't let an
x86 package write to x64 file registry locations as you've seen (logs
will show WIN64DUALFOLDERS modifying any property which references an
x64 location
And it's all a shame. I cane think of several use cases where it would be
useful and approriate for MSI to support 32 and 64 bit components in a single
install. To force seperation into multiple MSI's and logic into a setup.exe
is
just crazy. I should be able to do all of this with a
Thanks a lot for your reply. As I'm trying to get it to be done properly
anyway, I've suggested B or C. Well, C more strongly.
Good to know the experts agree ;-)
On 10-09-20 6:33 AM, Peter Shirtcliffe wrote:
You have a component rules violation. Windows Installer requires
different components
I am currently using WiX 3.5 in VS2010 and I am trying to make a custom output
path. I'm doing this so that when I change my product version from 1.2.0.0 to
1.3.0.0 it will create a folder under obj\release\1.3.0.0\ for the installation
files. This way, I can compile and keep different
The output path is an MSBuild concept. The pre-processor and other
variables are Wix concepts. You need to define your output path in terms
of MSBuild properties.
-Original Message-
From: Jonathan Ebersole [mailto:j...@compdevsys.com]
Sent: 20 September 2010 14:26
To:
Chris I agree with you, MSIs forced into being platform specific is pretty
ridiculous especially when taking .NET AnyCPU apps into account. I've been
forced to write some workarounds for the WIN64DUALFOLDERS issue where I'm
installing an x86 package to an x86 location but since the package is a
Hello Everyone,
I have an installer with a bootstrapper for .NET 3.5 and SQL server compact
3.5. But would like to upgrade the SQLCE to SQL Server Compact 3.5 Service
Pack 2. My installer needs to work offline and i am not sure how to
accomplish this.
I have the Bootstrapper Manifest
Thanks for your reply. Where/how would I set these MSBuild properties in the
WiX project? I also have a line item in my WiX .wxs file that lists the
product information. One of the properties is
Version=1.2.0.0
I haven't found a way for me to use the product version from my project
You mean having this file only once in your cabinet but installing it to
several places?
Then the DuplicateFile table is your friend!
kind regards,
fabio
On Mon, Sep 20, 2010 at 7:08 PM, Sean Farrow
sean.far...@seanfarrow.co.ukwrote:
Hi:
Is it possible when running a msi to install a file in
I have a wixproj that uses HeatDirectory to build the file references I need
for an MSI. It is running fine on my machine, but failing on the build server,
which is running Team Foundation Server 2010's Team Build. I have not
installed WiX on the build server, but instead checked the files in
Thanks for the replies. This sounds like a giant pain. It's horrible that I
can't tell the installer the exact directory that I want some files in. It
just changes it without telling me it's going to, and there is nothing I can
do to stop it. Couldn't they have at least made some kind of
Sorry Grant, no guided tours when your skiing the backcountry. You gotta be
able to hold your own on this one. :-) My only clues are to make sure you
understand the difference between SetProperty (51) and SetDirectory (35) custom
actions. How costing works and servicing implications for
When WIX is installed, it updates Visual Studio to provide, for example, a
C# custom action project type. This project type refers to
Microsoft.Deployment.WindowsInstaller.dll, and has a build action to run
MakeSfxCa.
How does Visual Studio know where that DLL resides? It's not in the GAC and
Hey all,
On the project I'm working on, we need MSI files to never have a UI (even
the built in one), other than the UAC dialog, pop up. This means when a user
double clicks the MSI file in Windows Explorer no dialog will pop up other
than the UAC one.
Is it possible to do this with Wix and if
Those settings are read from the registry in the msbuild .targets file if
the values for the variables are not provided in the msbuild environment.
For instance, see C:\Program Files
(x86)\MSBuild\Microsoft\WiX\v3.5\wix.targets, and look for the task
_SetDefaultPathValues.
If you want to use
25 matches
Mail list logo
