Re: [WiX-users] Wix 3.0 and Votive?

2007-02-09 Thread Bob Arnson
Matthew Rowan wrote:
> I am also interested in moving to WiX v3 from v2. I already have a 
> wixproj file I am maintaining for SharpDevelop and would like to move 
> this into Visual Studio. The only thing I am cautious of is that I 
> will need to do patch creation and on 
> http://wix.sourceforge.net/faq.html it has What's New in WiX v3 ... 
> Patch creation support (soon). Is this still the case, or is patch 
> creation in WiX v3 possible?

WiX v3 is adding the ability to create patches directly (e.g., light.exe 
producing .msp files). WiX v2 and v3 already support patch creation by 
creating .pcp files that you pass to MsiMsp/Patchwiz.

-- 
sig://boB
http://bobs.org



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Matthew Rowan

I am also interested in moving to WiX v3 from v2. I already have a wixproj
file I am maintaining for SharpDevelop and would like to move this into
Visual Studio. The only thing I am cautious of is that I will need to do
patch creation and on http://wix.sourceforge.net/faq.html it has What's New
in WiX v3 ... Patch creation support (soon). Is this still the case, or is
patch creation in WiX v3 possible?

Regards,

-Matthew Rowan
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Cullen Waters
Actually, for us, we use a common settings file  at the top of the file.

In the settings file, we have .  This element can be 
overridden in each project file.

If you go to the property pages for a wix project, there is a button on the 
compiler tab for Advanced Properties, or something like that.  Put your 
semicolon separated list in there.

Alternatively, if you like to edit XML by hand, you can right click on any 
project (for any project type, actually), and select unload project.  Once it's 
greyed out in solution explorer, right click again, and select Edit 
MyProj.wixproj.  It will open in the VS main window, with the XML editor open.

From: Scott Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 11:00 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

Sorry I'm kind of new to this.  Is that the msbuild file for the specific 
project correct?  Is there a way to edit that in VS/TFS?

From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 1:01 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

What I did was set a property called  in my MSBuild file.  
Then, when candle is executed, the WixTasks convert that semicolon separated 
list of variables into -d= when passed into the candle command 
line.  The only thing you might have to do is change the env. prefix to var., 
if nant was setting an environment variable for you.

From: Scott Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 8:58 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

Thanks, I've gotten the wxs files updated, and added them to the projects in 
TFS.  How do you handle the source path for the files being added to the msi?  
Before I used a nant variable in the wix as part of the path.  Is there a 
similar way to do this using MSBuild?  It looks like the path will change based 
on whether or not it is a debug or release build.

From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 1:54 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

I just moved my whole team from v2 to v3.

In general, the update went really smoothly.  You can use wixcop.exe to update 
all of the xml for you.  Wixcop doesn't, however remove shortnames, which might 
cause you some headaches.  I went through all my xml and manually deleted all 
the short names.

What might cause you some extra work, depending on how you use v2, is that v3 
runs msi validation as part of light.  We found a bunch of msival errors in our 
MSIs when we went to v3, and it took some time to work through them.  This is a 
good thing, though, since you have essentially raised the quality bar of your 
installers by doing this.

We use votive with VS Team Suite, and we haven't had any problems yet.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?

I was thinking of trying out votive.  We are using Visual Studio Team Edition 
for Developers with Team Foundation Server.  We are also using WIX v2  for the 
msi.  I was wondering, is Wix v3 stable enough to use if we are deploying our 
next version of our product in about 3-5 months.  Has anyone used votive with 
team foundation server?  Are there any problems to be expected when moving from 
wix v2 to wix v3?

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Justin Rockwood
You can edit that property () in the property pages if
you're using Votive. Just right mouse click the project in Solution Explorer
and click "Properties." Alternatively, you can edit the .wixproj file
directly and add Name=Value;Name2=Value2
within an existing . Make sense?

 

Justin

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday, February 07, 2007 11:00 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix 3.0 and Votive?

 

Sorry I'm kind of new to this.  Is that the msbuild file for the specific
project correct?  Is there a way to edit that in VS/TFS?

 

From: Cullen Waters [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 07, 2007 1:01 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

What I did was set a property called  in my MSBuild file.
Then, when candle is executed, the WixTasks convert that semicolon separated
list of variables into -d= when passed into the candle command
line.  The only thing you might have to do is change the env. prefix to
var., if nant was setting an environment variable for you.

 

From: Scott Sam [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 07, 2007 8:58 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

Thanks, I've gotten the wxs files updated, and added them to the projects in
TFS.  How do you handle the source path for the files being added to the
msi?  Before I used a nant variable in the wix as part of the path.  Is
there a similar way to do this using MSBuild?  It looks like the path will
change based on whether or not it is a debug or release build.

 

From: Cullen Waters [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 01, 2007 1:54 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

I just moved my whole team from v2 to v3.  

 

In general, the update went really smoothly.  You can use wixcop.exe to
update all of the xml for you.  Wixcop doesn't, however remove shortnames,
which might cause you some headaches.  I went through all my xml and
manually deleted all the short names.

 

What might cause you some extra work, depending on how you use v2, is that
v3 runs msi validation as part of light.  We found a bunch of msival errors
in our MSIs when we went to v3, and it took some time to work through them.
This is a good thing, though, since you have essentially raised the quality
bar of your installers by doing this.

 

We use votive with VS Team Suite, and we haven't had any problems yet.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?

 

I was thinking of trying out votive.  We are using Visual Studio Team
Edition for Developers with Team Foundation Server.  We are also using WIX
v2  for the msi.  I was wondering, is Wix v3 stable enough to use if we are
deploying our next version of our product in about 3-5 months.  Has anyone
used votive with team foundation server?  Are there any problems to be
expected when moving from wix v2 to wix v3?

 

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Scott Sam
Sorry I'm kind of new to this.  Is that the msbuild file for the
specific project correct?  Is there a way to edit that in VS/TFS?

 

From: Cullen Waters [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 07, 2007 1:01 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

What I did was set a property called  in my MSBuild
file.  Then, when candle is executed, the WixTasks convert that
semicolon separated list of variables into -d= when passed
into the candle command line.  The only thing you might have to do is
change the env. prefix to var., if nant was setting an environment
variable for you.

 

From: Scott Sam [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 07, 2007 8:58 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

Thanks, I've gotten the wxs files updated, and added them to the
projects in TFS.  How do you handle the source path for the files being
added to the msi?  Before I used a nant variable in the wix as part of
the path.  Is there a similar way to do this using MSBuild?  It looks
like the path will change based on whether or not it is a debug or
release build.

 

From: Cullen Waters [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 01, 2007 1:54 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

I just moved my whole team from v2 to v3.  

 

In general, the update went really smoothly.  You can use wixcop.exe to
update all of the xml for you.  Wixcop doesn't, however remove
shortnames, which might cause you some headaches.  I went through all my
xml and manually deleted all the short names.

 

What might cause you some extra work, depending on how you use v2, is
that v3 runs msi validation as part of light.  We found a bunch of
msival errors in our MSIs when we went to v3, and it took some time to
work through them.  This is a good thing, though, since you have
essentially raised the quality bar of your installers by doing this.

 

We use votive with VS Team Suite, and we haven't had any problems yet.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?

 

I was thinking of trying out votive.  We are using Visual Studio Team
Edition for Developers with Team Foundation Server.  We are also using
WIX v2  for the msi.  I was wondering, is Wix v3 stable enough to use if
we are deploying our next version of our product in about 3-5 months.
Has anyone used votive with team foundation server?  Are there any
problems to be expected when moving from wix v2 to wix v3?

 

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Cullen Waters
What I did was set a property called  in my MSBuild file.  
Then, when candle is executed, the WixTasks convert that semicolon separated 
list of variables into -d= when passed into the candle command 
line.  The only thing you might have to do is change the env. prefix to var., 
if nant was setting an environment variable for you.

From: Scott Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 8:58 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

Thanks, I've gotten the wxs files updated, and added them to the projects in 
TFS.  How do you handle the source path for the files being added to the msi?  
Before I used a nant variable in the wix as part of the path.  Is there a 
similar way to do this using MSBuild?  It looks like the path will change based 
on whether or not it is a debug or release build.

From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 1:54 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

I just moved my whole team from v2 to v3.

In general, the update went really smoothly.  You can use wixcop.exe to update 
all of the xml for you.  Wixcop doesn't, however remove shortnames, which might 
cause you some headaches.  I went through all my xml and manually deleted all 
the short names.

What might cause you some extra work, depending on how you use v2, is that v3 
runs msi validation as part of light.  We found a bunch of msival errors in our 
MSIs when we went to v3, and it took some time to work through them.  This is a 
good thing, though, since you have essentially raised the quality bar of your 
installers by doing this.

We use votive with VS Team Suite, and we haven't had any problems yet.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?

I was thinking of trying out votive.  We are using Visual Studio Team Edition 
for Developers with Team Foundation Server.  We are also using WIX v2  for the 
msi.  I was wondering, is Wix v3 stable enough to use if we are deploying our 
next version of our product in about 3-5 months.  Has anyone used votive with 
team foundation server?  Are there any problems to be expected when moving from 
wix v2 to wix v3?

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Simon Dahlbacka

follow this item:
http://sourceforge.net/tracker/index.php?func=detail&aid=1585281&group_id=105970&atid=642717


..and until that is fixed, you can probably define the variables yourself
appropriately..

Quote Justin:

As far as Votive is concerned, you can define the preprocessor variable by

entering >"Configuration=$(Configuration)" on the compiler property page
(not linker property page). Also, >make sure to put the parenthesis (which
you missed in your example below).

On 2/7/07, Scott Sam < [EMAIL PROTECTED]> wrote:


 Thanks, I've gotten the wxs files updated, and added them to the projects
in TFS.  How do you handle the source path for the files being added to the
msi?  Before I used a nant variable in the wix as part of the path.  Is
there a similar way to do this using MSBuild?  It looks like the path will
change based on whether or not it is a debug or release build.



*From:* Cullen Waters [mailto:[EMAIL PROTECTED]
*Sent:* Thursday, February 01, 2007 1:54 PM
*To:* Scott Sam; wix-users@lists.sourceforge.net
*Subject:* RE: [WiX-users] Wix 3.0 and Votive?



I just moved my whole team from v2 to v3.



In general, the update went really smoothly.  You can use wixcop.exe to
update all of the xml for you.  Wixcop doesn't, however remove shortnames,
which might cause you some headaches.  I went through all my xml and
manually deleted all the short names.



What might cause you some extra work, depending on how you use v2, is that
v3 runs msi validation as part of light.  We found a bunch of msival errors
in our MSIs when we went to v3, and it took some time to work through them.
This is a good thing, though, since you have essentially raised the quality
bar of your installers by doing this.



We use votive with VS Team Suite, and we haven't had any problems yet.



*From:* [EMAIL PROTECTED] [mailto:
[EMAIL PROTECTED] *On Behalf Of *Scott Sam
*Sent:* Thursday, February 01, 2007 10:47 AM
*To:* wix-users@lists.sourceforge.net
*Subject:* [WiX-users] Wix 3.0 and Votive?



I was thinking of trying out votive.  We are using Visual Studio Team
Edition for Developers with Team Foundation Server.  We are also using WIX
v2  for the msi.  I was wondering, is Wix v3 stable enough to use if we are
deploying our next version of our product in about 3-5 months.  Has anyone
used votive with team foundation server?  Are there any problems to be
expected when moving from wix v2 to wix v3?



-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-07 Thread Scott Sam
Thanks, I've gotten the wxs files updated, and added them to the
projects in TFS.  How do you handle the source path for the files being
added to the msi?  Before I used a nant variable in the wix as part of
the path.  Is there a similar way to do this using MSBuild?  It looks
like the path will change based on whether or not it is a debug or
release build.

 

From: Cullen Waters [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 01, 2007 1:54 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?

 

I just moved my whole team from v2 to v3.  

 

In general, the update went really smoothly.  You can use wixcop.exe to
update all of the xml for you.  Wixcop doesn't, however remove
shortnames, which might cause you some headaches.  I went through all my
xml and manually deleted all the short names.

 

What might cause you some extra work, depending on how you use v2, is
that v3 runs msi validation as part of light.  We found a bunch of
msival errors in our MSIs when we went to v3, and it took some time to
work through them.  This is a good thing, though, since you have
essentially raised the quality bar of your installers by doing this.

 

We use votive with VS Team Suite, and we haven't had any problems yet.

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?

 

I was thinking of trying out votive.  We are using Visual Studio Team
Edition for Developers with Team Foundation Server.  We are also using
WIX v2  for the msi.  I was wondering, is Wix v3 stable enough to use if
we are deploying our next version of our product in about 3-5 months.
Has anyone used votive with team foundation server?  Are there any
problems to be expected when moving from wix v2 to wix v3?

 

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


Re: [WiX-users] Wix 3.0 and Votive?

2007-02-01 Thread Cullen Waters
I just moved my whole team from v2 to v3.

In general, the update went really smoothly.  You can use wixcop.exe to update 
all of the xml for you.  Wixcop doesn't, however remove shortnames, which might 
cause you some headaches.  I went through all my xml and manually deleted all 
the short names.

What might cause you some extra work, depending on how you use v2, is that v3 
runs msi validation as part of light.  We found a bunch of msival errors in our 
MSIs when we went to v3, and it took some time to work through them.  This is a 
good thing, though, since you have essentially raised the quality bar of your 
installers by doing this.

We use votive with VS Team Suite, and we haven't had any problems yet.

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?

I was thinking of trying out votive.  We are using Visual Studio Team Edition 
for Developers with Team Foundation Server.  We are also using WIX v2  for the 
msi.  I was wondering, is Wix v3 stable enough to use if we are deploying our 
next version of our product in about 3-5 months.  Has anyone used votive with 
team foundation server?  Are there any problems to be expected when moving from 
wix v2 to wix v3?

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users