Sorry but I couldn't leave it...

1. I have to disagree, I'm sure you have a better inside track than me
but they do it because they want us to all have the same version, even
Office updates work this way. Policy files just don't cut it especially
if you do daily builds - you would need hundreds of them very quickly.
Office uses policy file to upgrade us from v11 to v12 which makes sense.

2. My GAC doesn't contain anything done the "right way" so I would have
to question why it is right.

Neil

-----Original Message-----
From: Rob Mensching [mailto:rob.mensch...@microsoft.com] 
Sent: 20 January 2009 15:55
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Getting the version from the Assembly file

The "assemblyFileVersion" is only applicable when installing into the
GAC.  Otherwise, AFAIK, standard file versioning rules apply.  The
guidance is to use publisher policy instead of "assemblyFileVersion"
when installing to the GAC.  Also, as it has been related to me, those
90% of Microsoft assemblies fall into two buckets:

1.  Core runtime stuff that can't be affected by publisher policy
(something has to process it).

2.  Microsoft teams doing the wrong thing.

Using the argument, "But Microsoft does it" will not always make you
right.  <smile/>

-----Original Message-----
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, January 19, 2009 23:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Getting the version from the Assembly file

>> 2.  My understanding of the .NET Framework documentation does not
recommend setting the "fileVersion" in the assembly identity.  They
recommend SxS semantics by upgrading the assembly's "version" only.

Apologies for going off topic but... I think this is true but rarely
practical, in reality you often need to upgrade in place and policy
redirects don't help - they are only really useful for redirection
between major versions. If you take a look in the GAC I think you will
find that 90% of what Microsoft ships has different file and assembly
versions.

Neil

Neil Sleightholm
X2 Systems Limited
n...@x2systems.com



------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------
------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to