From: Bob Arnson
Sent: Wed 8/2/2006 8:44 AM
>
> Derek Cicerone wrote:
> > I've done some more thinking about this. I think Rob's main objection with
> > making Product/@Id optional was that someone might accidentally forget to
> > specify it. However, what if we displayed a warning to the user whenever
> > they omitted the Property/@Id attribute informing them that doing so is
> > non-standard and would result in generating a new ProductCode for each build
> > - thus making it impossible to do anything other than major upgrades.
>
> Why should that be a warning?
I agree totally. As far as I'm concerned this is a useful feature. I want to be sure the ProductCode changes every time, to ensure that it is impossible to do anything other than major upgrades. This may be an unusual requirement, but it's a valid one and I shouldn't like to see a warning for it.
I'm sure mine isn't the only environment where warnings are forbidden in production builds. If this were to generate a warning, the warning ought to be very specific to this case, and it should be possible to suppress this one warning from the command line. Even that's messy though - I'd far rather there not be a warning for this.
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
