RE: [WiX-users] Observations as a current WiX user...

(Adding wix-devs list)


1. and 3. are on their way (code written and working on my machine and
in my usage scenario), but rely on the CodeDOM and .NET framework 2.0 so
are not ready for inclusion in WiX "as is".

=20

I'm not sure if tallow is the right place to put it, though. Because:

1.	I don't like the idea of one tool that does everything using 100
different command line switched. For me, its easier to remember
"autocomplete myfile1.wxs myfile2.wxs myfile3.wxs" than "tallow /a
myfile.wxs", for example.=20
2.	Tallow generates code - this completes code

=20

Once CodeDOM can support InnerText and comments and my WiX copyright
assignment agreement is fully processed by Microsoft, I'll submit the
code for inclusion with WiX.=20

=20

Does WiX have a policy on using .NET 2.0 code once it becomes available?
Eg, will WiX stay completely on .NET 1.1 or will WiX accept code that
runs on .NET 2.0?=20

=20

Frederik.

=20

=20

________________________________

Van: Rob Mensching [mailto:ro...@us...]=20
Verzonden: maandag 25 juli 2005 19:14
Aan: Frederik Carlier; wix...@li...
Onderwerp: RE: [WiX-users] Observations as a current WiX user...

=20

1.  Your first suggestion is pretty interesting.  Maybe that feature
could be added to tallow.exe?  Interested in trying to do that?  Even if
not, it'd probably be a good idea to get captured in a Feature Request.

=20

2.  Agreed.  GUIDs should not be accepted in all the typical forms
allowed.

=20

3.  Again, adding this to tallow could be interesting and I'm still
looking for the right way to have candle/light do this automatically (if
that is possible).=20

=20

________________________________

From: wix...@li...
[mailto:wix...@li...] On Behalf Of Frederik
Carlier
Sent: Wednesday, July 13, 2005 2:38 AM
To: wix...@li...
Subject: RE: [WiX-users] Observations as a current WiX user...

=20

What about yet another tool that takes a WiX source file and
automatically inserts GUIDs wherever they are omitted. Since the GUIDs
are added to the WiX source file directly, they'll remain constant over
time. It just takes the burden off the developer's shoulders to generate
all those guids.

=20

And it would be amazingly useful if WiX supported GUIDs in the COM+
style!

=20

A similar approach as mentioned above could be used for handling the 8.3
file names: a tool that you would run your wxs files through and that
tool would add the 8.3 filename property, preferably using the Windows
file name conventions. This resolves, again, the stability issues
described earlier in this thread.=20

=20

Frederik.

=20

________________________________

Van: Rob Mensching [mailto:ro...@us...]=20
Verzonden: dinsdag 12 juli 2005 22:50
Aan: 'Jerry Dennany'; wix...@li...
Onderwerp: RE: [WiX-users] Observations as a current WiX user...

=20

Yeah, I wasn't clear (maybe have never been clear).  I absolutely
believe that we need to come up with a very good way to manage all of
the GUIDs.  The current system is the simplest and safest (from the
tool's point of view) but far from the easiest and doesn't *really* help
developers be safe with their Component/@Ids.

=20

Fundamentally, I agree that this is a hard problem that needs solving
but bugs where WiX produces incorrect output are still my priority.
<smile/>

=20

________________________________

From: wix...@li...
[mailto:wix...@li...] On Behalf Of Jerry
Dennany
Sent: Tuesday, July 12, 2005 12:22 PM
To: wix...@li...
Subject: RE: [WiX-users] Observations as a current WiX user...

=20

Rob - thanks for the detailed response, along with the clarification of
some misunderstandings.

=20

=20

One comment - there seems to be a common theme against auto-generation
in the compiler.  I certainly understand your argument. Perhaps we
should agree that the compiler isn't the best location for
auto-generation of Ids, or GUIDs, or (most) anything else.

=20

However, somewhere in the toolset chain there should be an 'easy' way to
accomplish many of these redundant tasks.  Whether it's through
IntelliCrack in votive, or command line options in dark.exe, or a yet
un-developed GUI wizard, this isn't really something that should have to
be hand crafted.

=20

Thanks much,

=20

-Jerry