Each Directory/@Id value is also a property that is the full path to that
directory. If you don't supply the path for any one of those properties, then
Windows Installer will create them based on the @Name values and the relative
positions of the directories. That is what allows to make Bar =
oops... you're right. the guys converting the projects to vs 2010 changed
the project name...
-Original Message-
From: Helge Kruse [mailto:helge.kruse-nos...@gmx.net]
Sent: Tuesday, May 03, 2011 12:53 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Un
Am 03.05.2011 18:30, schrieb Kurt Jensen:
> The full command line contains over 70 other projects with variable
> definitions all of which contain one or more "."
>
> None of the other $(var.Spiricon..TargetPath) is listed as an
> error.
>
>
>> -dSpiricon.Factory.Manager.TargetPath=E:\BaseI\CodeBas
Thanks for the reply. AFAIK, if I have a wix directory structure defined as:
.
.
< Directory Id = "Bar" Name="Bar">
.
.
On installation, I should see the directory structure ...\Foo\Bar\ Since
'Bar' in this case is considered relative to 'Foo', why is it not in my case
mentioned be
The full command line contains over 70 other projects with variable
definitions all of which contain one or more "."
None of the other $(var.Spiricon..TargetPath) is listed as an
error.
-Original Message-
From: Dick Van den Brink [mailto:d_vandenbr...@live.com]
Sent: Tuesday, May 03, 201
Firstly a verbose log would tell you exactly what the problem is.
Secondly run the following command msiexec /i setup.msi INSTALLPATH="C:\Cool"
SUBFOLDER="C:\Cool\Ice" and I suspect it'll work as you expect.
SUBFOLDER refers to a Property being used as a Directory Identifier. It still
needs to
That was what I was trying to avoid, but it seems there's no other way. I've
actually got a fairly fully featured wix lib that takes care of everything
for me automatically, but I was hoping to avoid doing the bunch of
copy/paste that apparently is required.
Thank you for your insight.
On May 3, 2
I think it's confused because of the ".".
When I create a WiX project in Visual Studio and add a reference to a project
called Test.Project.Then i need to change the reference name (in the package
project) to TestProject in order to access the variables.
> From: kurt.jen...@us.ophiropt.com
> D
converting a v3.0 project to v3.5.
on the command line I find the following.
…
dSpiricon.Export.TargetDir=E:\BaseI\CodeBase\Applications\Assemblies\
-dSpiricon.Export.TargetExt=.dll
-dSpiricon.Export.TargetFileName=Spiricon.Export.dll
-dSpiricon.Export.TargetName=Spiricon.Export
-dSpiricon.E
Hi,
I want to generate an .MSI which places a file, snow.txt, in the folder
(INSTALLPATH)\(SUBFOLDER)\ where INSTALLPATH and SUBFOLDER are public
properties that are defined from command line:
msiexec /i setup.msi INSTALLPATH="C:\Cool" SUBFOLDER="Ice"
I was trying to get my WiX working but it
converting a v3.0 project to v3.5.
on the command line I find the following.
…
dSpiricon.Export.TargetDir=E:\BaseI\CodeBase\Applications\Assemblies\
-dSpiricon.Export.TargetExt=.dll
-dSpiricon.Export.TargetFileName=Spiricon.Export.dll
-dSpiricon.Export.TargetName=Spiricon.Export
-dSpiricon.E
11 matches
Mail list logo
