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
