Re: [WiX-users] Future of Votive?
Is there a way of specifying the -b switch when building from Visual Studio? Assuming you mean using Votive, it doesn't appear to be exposed through the project property pages. But you can edit the .wixproj file outside VS and add a LinkerBaseInputPaths property to be a semi-colon-delimited list of paths. Would adding this to the light property page be the kind of thing that patches would be welcome for? Regards, John - 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
Re: [WiX-users] Future of Votive?
John Hall wrote: Would adding this to the light property page be the kind of thing that patches would be welcome for? I won't speak for Justin but in general, patches are pretty much always welcome.g -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Future of Votive?
Bob Arnson wrote I don't think there's a switch in there currently to do relative paths. Typically that's when I switch to search replace. You can also omit the Source attribute entirely, if the file is in the directory indicated by the Directory element hierarchy and has the same name. The binder can use the -b switch to Light to determine where to start looking for files. Bob, Is there a way of specifying the -b switch when building from Visual Studio? Regards, John - 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
Re: [WiX-users] Future of Votive?
But you can use the 'references' feature in votive to make the process easier. For example, if you have a solution that contains two source projects - MySource1 and MySource2, plus the WiX Installer project you can add project references in the WiX project to MySource1 and MySource2. You can then reference the source in WiX as: $(var.MySource1.TargetPath) (amongst other options - TargetDir, etc.). Bob Arnson-6 wrote: Christopher Painter wrote: Is there a switch to Heat that tells it to not create a source attribute? Not currently. -- sig://boB http://joyofsetup.com/ - 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 -- View this message in context: http://www.nabble.com/Future-of-Votive--tf3893120.html#a11062294 Sent from the wix-users mailing list archive at Nabble.com. - 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
Re: [WiX-users] Future of Votive?
John Hall wrote: Is there a way of specifying the -b switch when building from Visual Studio? Assuming you mean using Votive, it doesn't appear to be exposed through the project property pages. But you can edit the .wixproj file outside VS and add a LinkerBaseInputPaths property to be a semi-colon-delimited list of paths. -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Future of Votive?
I've never worked anywhere that the developers *wanted* to have anything to do with installers. No offence to developers in general, but it's an easy thing to screw up and they have bigger fish to fry. I find when you have too many cooks in that kitchen they inevitably step on each other, and someone ends up having to re-check the work. Installers are a quirky thing and I wouldn't expect all my developers to know the ins and outs of whatever tool we happen to be using. As a CM guy, I usually wrestle away the function of writing the installers from whoever has it when I start a new job. When a deployment goes bad, it's usually the CM guy that gets blamed. So it makes sense to me to put it in that group, or at the very least have a single author involved in making the installers. I've worked at one place that was big enough that we had a group (okay, two people) that only did installers. That being said, referring back to the original question, there is a GUI out there called WixEdit that has a lot of great functionality and is most excellent for constructing your initial installer(s). I used it to make the template for all our installers and fire it up once in a while to do tedious work (especially editing dialogs with the GUI editor! Sweet!) You should check it out. It doesn't 'plug in' to VS, it's a standalone app, but it's worth looking into. http://wixedit.sourceforge.net/ -Matt _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Painter Sent: Sunday, June 10, 2007 4:31 PM To: Jared Ashman; Bob Arnson Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Future of Votive? Ok, I like this since I think it makes alot of sense for your SCM / staging structure to mirror your deployment strucutre. Is there a switch to Heat that tells it to not create a source attribute? My developers really aren't interested in doing search/replace, running XML cleanup scripts to remove an attribute from every element or search through source code to find a switch that isn't documented in the help. They need to keep it simple so they can add a file and getting back to coding. Jared Ashman [EMAIL PROTECTED] wrote: Now that's cool. Thanks for the tip! On 6/10/07, Bob Arnson [EMAIL PROTECTED] wrote: Jared Ashman wrote: I don't think there's a switch in there currently to do relative paths. Typically that's when I switch to search replace. You can also omit the Source attribute entirely, if the file is in the directory indicated by the Directory element hierarchy and has the same name. The binder can use the -b switch to Light to determine where to start looking for files. -- sig://boB http://joyofsetup.com/ _ Ready for the edge of your seat? Check out tonight's top picks http://us.rd.yahoo.com/evt=48220/*http:/tv.yahoo.com/ on Yahoo! TV. - 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
Re: [WiX-users] Future of Votive?
I agree with you, on a continuum of centralized --- decentralized, I am very
much of the same mind set as you. However I do see an opprotunity/need to
slide down that line a little bit and decentralize some of the simpler aspects
of the installs ( support files xcopy type pattern ) and I see a WiX based tool
that plugs into VS, MSBuild and has simplified designers as the way to go.
Thanks,
Chris
Matthew Janulewicz [EMAIL PROTECTED] wrote:
v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);}
Ive never worked anywhere that the developers *wanted* to have
anything to do with installers. No offence to developers in general, but its
an easy thing to screw up and they have bigger fish to fry. I find when you
have too many cooks in that kitchen they inevitably step on each other, and
someone ends up having to re-check the work. Installers are a quirky thing and
I wouldnt expect all my developers to know the ins and outs of whatever tool
we happen to be using.
As a CM guy, I usually wrestle away the function of writing the installers
from whoever has it when I start a new job. When a deployment goes bad, its
usually the CM guy that gets blamed. So it makes sense to me to put it in that
group, or at the very least have a single author involved in making the
installers. Ive worked at one place that was big enough that we had a group
(okay, two people) that only did installers.
That being said, referring back to the original question, there is a GUI out
there called WixEdit that has a lot of great functionality and is most
excellent for constructing your initial installer(s). I used it to make the
template for all our installers and fire it up once in a while to do tedious
work (especially editing dialogs with the GUI editor! Sweet!) You should check
it out. It doesnt plug in to VS, its a standalone app, but its worth
looking into.
http://wixedit.sourceforge.net/
-Matt
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christopher
Painter
Sent: Sunday, June 10, 2007 4:31 PM
To: Jared Ashman; Bob Arnson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Future of Votive?
Ok, I like this since I think it makes alot of sense for your SCM / staging
structure to mirror your deployment strucutre. Is there a switch to Heat that
tells it to not create a source attribute?
My developers really aren't interested in doing search/replace, running
XML cleanup scripts to remove an attribute from every element or search through
source code to find a switch that isn't documented in the help.They need to
keep it simple so they can add a file and getting back to coding.
Jared Ashman [EMAIL PROTECTED] wrote:
Now that's cool. Thanks for the tip!
On 6/10/07, Bob Arnson [EMAIL PROTECTED] wrote:
Jared Ashman wrote:
I don't think there's a switch in there currently to do relative
paths. Typically that's when I switch to search replace.
You can also omit the Source attribute entirely, if the file is in the
directory indicated by the Directory element hierarchy and has the same
name. The binder can use the -b switch to Light to determine where to
start looking for files.
--
sig://boB
http://joyofsetup.com/
-
Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV.
-
Building a website is a piece of cake.
Yahoo! Small Business gives you all the tools to get online.-
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
Re: [WiX-users] Future of Votive?
I don't think there's a switch in there currently to do relative paths. Typically that's when I switch to search replace. Heat's not meant to do all your work for you, just give a solid base and decrease the amount of initial setup time. As to documentation on the -gg switch, I found out about -gg from this mailing list a few months ago, there are a few other switches that are undocumented. I think someone said to basically go and read the source to find them if you're interested. Or a search through the archives may turn some information up. On 6/9/07, Christopher Painter [EMAIL PROTECTED] wrote: Is there a switch to tell it to use Relative Paths for the Source Attribute or is that search and replace time? Btw, -gg isn't documented when you say heat /? Where is that documented? *Jared Ashman [EMAIL PROTECTED]* wrote: Not sure about the Votive information, but if you pass -gg to heat as an option it will generate guids for you instead of inserting the PUT-GUID-HERE message. On 6/8/07, Christopher Painter [EMAIL PROTECTED] wrote: I've been playing with Votive and I really like the way it plugs into VS and uses MSBuild. My installs are primarily InstallShield based, and they will remain that way, but I would like to break some of the xcopy type logic out into seperate merge modules and let developers maintain them. My developers looked at Votive and basically said that they have no intention of entering raw xml to maintaing the dir/file trees associated with these merge modules. Will Votive ever have a Right Click | View Designer feature? The perfect tool for me would take the VS features the Votive already has and give a vey simple drag and drop approach to directory structure creation similar to the way VDPROJ does it. The tool would need to automaically generate relative path file links and be very careful to not let developers do stupid things. We are trying to support minor upgrades so features like `deprecate file` to cause transitive style puncturing of components would be really good. I tried playing with heat but my developer don't want to have to use the command line and they want to be able to easily add and remove from the tree as needed. Eitherway I have a question about heat I notice that it sets components to Guid=PUT-GUID-HERE and uses absolute paths instead of relative paths in the Source attribute. When you import a large directory structure, whats the easiest way to update those? It seems very annonying to have to go through hundreds of these to get an WXS file that will properly work. -- Looking for a deal? Find great prices on flights and hotelshttp://us.rd.yahoo.com/evt=47094/*http://farechase.yahoo.com/;_ylc=X3oDMTFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20-with Yahoo! FareChase. - 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 -- Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://us.rd.yahoo.com/evt=48224/*http://sims.yahoo.com/ - 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
Re: [WiX-users] Future of Votive?
Jared Ashman wrote: I don't think there's a switch in there currently to do relative paths. Typically that's when I switch to search replace. You can also omit the Source attribute entirely, if the file is in the directory indicated by the Directory element hierarchy and has the same name. The binder can use the -b switch to Light to determine where to start looking for files. -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Future of Votive?
Now that's cool. Thanks for the tip! On 6/10/07, Bob Arnson [EMAIL PROTECTED] wrote: Jared Ashman wrote: I don't think there's a switch in there currently to do relative paths. Typically that's when I switch to search replace. You can also omit the Source attribute entirely, if the file is in the directory indicated by the Directory element hierarchy and has the same name. The binder can use the -b switch to Light to determine where to start looking for files. -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Future of Votive?
Ok, I like this since I think it makes alot of sense for your SCM / staging structure to mirror your deployment strucutre. Is there a switch to Heat that tells it to not create a source attribute? My developers really aren't interested in doing search/replace, running XML cleanup scripts to remove an attribute from every element or search through source code to find a switch that isn't documented in the help.They need to keep it simple so they can add a file and getting back to coding. Jared Ashman [EMAIL PROTECTED] wrote: Now that's cool. Thanks for the tip! On 6/10/07, Bob Arnson [EMAIL PROTECTED] wrote: Jared Ashman wrote: I don't think there's a switch in there currently to do relative paths. Typically that's when I switch to search replace. You can also omit the Source attribute entirely, if the file is in the directory indicated by the Directory element hierarchy and has the same name. The binder can use the -b switch to Light to determine where to start looking for files. -- sig://boB http://joyofsetup.com/ - Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. - 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
Re: [WiX-users] Future of Votive?
Christopher Painter wrote: Is there a switch to Heat that tells it to not create a source attribute? Not currently. -- sig://boB http://joyofsetup.com/ - 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
Re: [WiX-users] Future of Votive?
Yes, there are plans to add designers to Votive. It's been on my list for a while, but unfortunately my spare time has been rare the past few months. I think the first designers will probably be very basic and rudimentary (I'm thinking of registry and file/directory editors), but eventually more will come. The challenging part will be to create the architecture for supporting designer extensions. So, for example, somebody writes a Wix extension to work with Media Center. They could also write an editor for that same extension and have it plug into Votive automatically once the extension is referenced from the wixproj. All sorts of cool ideas, but it'll probably be a while before they're in at the rate I'm going, unfortunately. Anyway, thanks for your suggestions. It's stuff that's already on my radar, but it's good to know that other people want it, too. Justin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jared Ashman Sent: Friday, June 08, 2007 9:47 PM To: Christopher Painter Cc: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Future of Votive? Not sure about the Votive information, but if you pass -gg to heat as an option it will generate guids for you instead of inserting the PUT-GUID-HERE message. On 6/8/07, Christopher Painter [EMAIL PROTECTED] wrote: I've been playing with Votive and I really like the way it plugs into VS and uses MSBuild. My installs are primarily InstallShield based, and they will remain that way, but I would like to break some of the xcopy type logic out into seperate merge modules and let developers maintain them. My developers looked at Votive and basically said that they have no intention of entering raw xml to maintaing the dir/file trees associated with these merge modules. Will Votive ever have a Right Click | View Designer feature? The perfect tool for me would take the VS features the Votive already has and give a vey simple drag and drop approach to directory structure creation similar to the way VDPROJ does it. The tool would need to automaically generate relative path file links and be very careful to not let developers do stupid things. We are trying to support minor upgrades so features like `deprecate file` to cause transitive style puncturing of components would be really good. I tried playing with heat but my developer don't want to have to use the command line and they want to be able to easily add and remove from the tree as needed. Eitherway I have a question about heat I notice that it sets components to Guid=PUT-GUID-HERE and uses absolute paths instead of relative paths in the Source attribute. When you import a large directory structure, whats the easiest way to update those? It seems very annonying to have to go through hundreds of these to get an WXS file that will properly work. _ Looking for a deal? Find great prices on flights and hotels http://us.rd.yahoo.com/evt=47094/*http:/farechase.yahoo.com/;_ylc=X3oDMTFic DJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20- with Yahoo! FareChase. - 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
Re: [WiX-users] Future of Votive?
Is there a switch to tell it to use Relative Paths for the Source Attribute or is that search and replace time? Btw, -gg isn't documented when you say heat /? Where is that documented? Jared Ashman [EMAIL PROTECTED] wrote: Not sure about the Votive information, but if you pass -gg to heat as an option it will generate guids for you instead of inserting the PUT-GUID-HERE message. On 6/8/07, Christopher Painter [EMAIL PROTECTED] wrote:I've been playing with Votive and I really like the way it plugs into VS and uses MSBuild. My installs are primarily InstallShield based, and they will remain that way, but I would like to break some of the xcopy type logic out into seperate merge modules and let developers maintain them. My developers looked at Votive and basically said that they have no intention of entering raw xml to maintaing the dir/file trees associated with these merge modules. Will Votive ever have a Right Click | View Designer feature? The perfect tool for me would take the VS features the Votive already has and give a vey simple drag and drop approach to directory structure creation similar to the way VDPROJ does it. The tool would need to automaically generate relative path file links and be very careful to not let developers do stupid things. We are trying to support minor upgrades so features like `deprecate file` to cause transitive style puncturing of components would be really good. I tried playing with heat but my developer don't want to have to use the command line and they want to be able to easily add and remove from the tree as needed. Eitherway I have a question about heat I notice that it sets components to Guid=PUT-GUID-HERE and uses absolute paths instead of relative paths in the Source attribute. When you import a large directory structure, whats the easiest way to update those? It seems very annonying to have to go through hundreds of these to get an WXS file that will properly work. - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. - 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 - Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. - 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
Re: [WiX-users] Future of Votive?
Not sure about the Votive information, but if you pass -gg to heat as an option it will generate guids for you instead of inserting the PUT-GUID-HERE message. On 6/8/07, Christopher Painter [EMAIL PROTECTED] wrote: I've been playing with Votive and I really like the way it plugs into VS and uses MSBuild. My installs are primarily InstallShield based, and they will remain that way, but I would like to break some of the xcopy type logic out into seperate merge modules and let developers maintain them. My developers looked at Votive and basically said that they have no intention of entering raw xml to maintaing the dir/file trees associated with these merge modules. Will Votive ever have a Right Click | View Designer feature? The perfect tool for me would take the VS features the Votive already has and give a vey simple drag and drop approach to directory structure creation similar to the way VDPROJ does it. The tool would need to automaically generate relative path file links and be very careful to not let developers do stupid things. We are trying to support minor upgrades so features like `deprecate file` to cause transitive style puncturing of components would be really good. I tried playing with heat but my developer don't want to have to use the command line and they want to be able to easily add and remove from the tree as needed. Eitherway I have a question about heat I notice that it sets components to Guid=PUT-GUID-HERE and uses absolute paths instead of relative paths in the Source attribute. When you import a large directory structure, whats the easiest way to update those? It seems very annonying to have to go through hundreds of these to get an WXS file that will properly work. -- Looking for a deal? Find great prices on flights and hotelshttp://us.rd.yahoo.com/evt=47094/*http://farechase.yahoo.com/;_ylc=X3oDMTFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20-with Yahoo! FareChase. - 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
