From: John V. <JVo...@mv...> - 2006-01-30 01:37:19
|
I hate to complain about a volunteer effort, please think of this as constructive criticism. Overall, I think WiX is great but a couple of the things you said about 3.0 didn't exactly thrill me. First, why is File/@LongName deprecated? Generating short names is a great feature but, some of us specifically enter long and short names, is that deprecated? Why? Also, WiXCop sounds like a great idea but not if it's going to dictate my indentation size and usage of white space. Why would it do that? Thanks, John Vottero > -----Original Message----- > From: wix...@li...=20 > [mailto:wix...@li...] On Behalf Of=20 > Derek Cicerone > Sent: Sunday, January 29, 2006 5:08 PM > To: 'Thomas Tomiczek'; wix...@li... > Subject: RE: [WiX-users] (no subject) >=20 > It's completely up to you to decide if/when 3.0 is right for=20 > you. We are > officially suggesting people stay off it, at least for now=20 > because there > hasn't really been any good testing yet. This is mostly due=20 > to the fact > that no one is using it yet. So it's a bit of problem=20 > because we need some > adventurous people to start using it in order to get the=20 > quality up. We'd > prefer that these adventurous groups having a ship date that=20 > is pretty far > out in the future so that if they hit a problem, we have=20 > ample time to fix > the issue properly. >=20 > Another big problem with moving to 3.0 too early is that the=20 > schema is being > moved around a little bit. The File/@LongName attribute is=20 > deprecated, > FragmentRef is deprecated, nesting Registry elements under=20 > one another will > be deprecated, all server-based elements like WebPool,=20 > WebSite, ... have > moved into an extension, etc... If you move to 3.0 now, you=20 > risk having to > update your source code every time you take a new drop of the=20 > toolset in > order to keep it working properly. Now, we've made a tool=20 > called WixCop > which can automate updating your code to these latest=20 > schemas, but it will > also completely dictate the style of your code be 2-space indentation, > double-quotes for attributes, and no unnecessary whitespace. =20 > So it's a bit > disruptive the first time you use WixCop. >=20 > Another problem with moving to 3.0 is that the wixlib and=20 > wixout files it > produces are not compatible with WiX 2.0. You can use a=20 > wixlib file from > 2.0 in 3.0, but not the other way around. The wixout files=20 > are completely > incompatible. So if you send wixlib files to another team,=20 > they need to > upgrade to the same version of 3.0 that you are on in order=20 > to be able to > use it. >=20 > Derek >=20 > -----Original Message----- > From: wix...@li... > [mailto:wix...@li...] On Behalf Of=20 > Thomas Tomiczek > Sent: Sunday, January 29, 2006 9:28 AM > To: wix...@li... > Subject: [WiX-users] (no subject) >=20 > Hm, when do you think people with some adventuring willingness could > start using Wix 3.0? It looks like Wix 3.0 will finally have some > serious advantages over all the other stuff. As our setups=20 > are currently > REALLY simple in their feature set (and it does not look like we are > going to have a lot more complex stuff like db setup etc.=20 > soon), I would > rather willingly try Wix 3.0. >=20 > ESPECIALLY when we talk about features like getting rid of=20 > the terrible > short names :-) >=20 > I hope you check that one in soon. I have a couple of setups to make > here. Inherently simple (create folder, copy dll's in, some shortcuts, > some file stuff). Still I would really love and prefer not to have to > deal with the idiocy of short file names. So your fix sort of=20 > really is > something I am drooling for. >=20 > Thomas >=20 > > -----Original Message----- > > From: wix...@li...=20 > > [mailto:wix...@li...] On Behalf Of=20 > > Derek Cicerone > > Posted At: Freitag, 27. Januar 2006 02:23 > > Posted To: wix-users > > Conversation: [WiX-users] Any ETA on the Short=20 > > Filenames=3DAutogeneratedHash fix? > > Subject: RE: [WiX-users] Any ETA on the Short=20 > > Filenames=3DAutogeneratedHash fix? > >=20 > >=20 > > This is a WiX 3.0-only feature. We are currently=20 > > discouraging people from using WiX 3.0 until next year=20 > > because this is the active development branch (for instance -=20 > > I recently found a two big problems with auto-generation of=20 > > registry identifiers). WiX 2.0 should be the toolset for all=20 > > products shipping this year. > >=20 > > Beyond these warnings, I'm still holding onto the fix because=20 > > I'm worried that I'm missing something (I'm not sure what -=20 > > it's just an intuition). We also need to have some=20 > > discussions about how this affects the nomenclature of other=20 > > attributes like Directory/@Name and Directory/@LongName. =20 > > I'll try to get it checked in within the next month. > >=20 > > Derek > >=20 > > -----Original Message----- > > From: wix...@li... > > [mailto:wix...@li...] On Behalf Of=20 > > Thomas Tomiczek > > Sent: Thursday, January 26, 2006 1:36 AM > > To: wix...@li... > > Subject: [WiX-users] Any ETA on the Short=20 > > Filenames=3DAutogeneratedHash fix? > >=20 > > OK :-) > >=20 > > Anyone has an ETA (estimated time of arrival) when we will=20 > > see the automated generation of short filenames in a build? I=20 > > am ready to start WIX installers for about half a dozen=20 > > projects here, and that is pretty much a "taking half the=20 > > work" from me thing. Like most others here we do not support=20 > > installation on short filenam only file systems by any mean=20 > > (due to the fact that our applications simply would not run=20 > > anyway), and having them to be determined was something that=20 > > really got on my nerves left and right in the whole windows=20 > > installer experience till now - from Installshield to Wise. > >=20 > > Thomas > >=20 > >=20 > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > > through log files for problems? Stop! Download the new AJAX=20 > > search engine that makes searching your log files as easy as=20 > > surfing the web. DOWNLOAD SPLUNK! > > = http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > > _______________________________________________ > > WiX-users mailing list > > WiX...@li... > > https://lists.sourceforge.net/lists/listinfo/wix-users > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > > through log files for problems? Stop! Download the new AJAX=20 > > search engine that makes searching your log files as easy as=20 > > surfing the web. DOWNLOAD SPLUNK! > > = http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > > _______________________________________________ > > WiX-users mailing list > > WiX...@li... > > https://lists.sourceforge.net/lists/listinfo/wix-users > >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. =20 > DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > WiX-users mailing list > WiX...@li... > https://lists.sourceforge.net/lists/listinfo/wix-users >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. =20 > DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > WiX-users mailing list > WiX...@li... > https://lists.sourceforge.net/lists/listinfo/wix-users >=20 |