I am using the WiX and Votive from v2, so I would think this problem would
exist right.
On 4/28/07, Justin Rockwood <[EMAIL PROTECTED]> wrote:
It depends on what build you're using. I recently checked in a fix (a
couple of weeks ago) where some property changes would not mark the project
as dirty, so they wouldn't save. I think things should be working now,
though. Let me know if you find that you're still having problems with
changes not getting saved correctly.
Thanks,
Justin
*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Anthony Wieser
*Sent:* Friday, April 27, 2007 11:56 PM
*To:* wix-users@lists.sourceforge.net
*Subject:* Re: [WiX-users] Pass variable's value using MSBuild (and a
votive problem)
If you're using Votive, go to the property pages, and add
SOURCEPATH=\\droplocation\sourcecode
to your define variables.
I had a lot of problems getting the values to stick for my project
configurations, so ended up doing it manually in the wixproj file, as
described below in my original reply. There seems to be some confusion
between the project the property page is modifying, and the one that visual
studio is claiming is current in its toolbar.
Has anyone else noticed that Votive doesn't like to save changed pages,
and figured out what provokes the problem.
Anthony Wieser
Wieser Software Ltd
So if I had a dropLocation that is used as a variable in my wxs file as
<?define SOURCEPATH =\\dropLocation\sourcecode?>
which is used in the wxs project as
<File Id="FileWebConfig" Name="WEB~1.CON" LongName="Web.config" src="$(
var.SOURCEPATH)\Web.config" />
How would I make this part of my MSBuild?
I want to use the MSBuild's droplocation as input to the wixproj which
here is the value for the SOURCEPATH. Can you elaborate help out here?
Thanks,
SJ
On 4/27/07, *Anthony Wieser* <[EMAIL PROTECTED]> wrote:
I'm had problems with this too.
I've had the following line in my .wixproj file:
<WixVariables>Config=" demo.wxi"</WixVariables>
Then in my .wxs file, I'd like to include the file specified as config.
I tried this in my .wxs file,
<?include $(var.Config) ?>
but I get this error:
Error CNDL0150: Undefined preprocessor variable '$( var.Config)'.
Then I looked around, and discovered, that this passes a LINKER variable.
To pass a compiler variable I need to do this instead:
<DefineConstants>Config=demo.wxi</DefineConstants>
Now it works as expected.
Anthony Wieser
Wieser Software Ltd
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
