.Net Compact Framework: Versioning, Strong Names and the Global Assembly Cache – Part 1

re: .Net Compact Framework: Versioning, Strong Names and the Global Assembly Cache – Part 1

Robert Hurlbut — Thu, 01 Jul 2004 01:04:00 GMT

Welcome aboard! And, thanks for the intro into these important security topics as related to the Compact Framework.

re: .Net Compact Framework: Versioning, Strong Names and the Global Assembly Cache – Part 1

Chris Auld — Thu, 01 Jul 2004 01:33:00 GMT

I'd be keen to see some stuff on how the GC differs from the desktop framework.

re: .Net Compact Framework: Versioning, Strong Names and the Global Assembly Cache – Part 1

Neil Cowburn — Tue, 06 Jul 2004 23:02:00 GMT

This is all good stuff! Keep it coming. The info about version binding granuality should be required reading for all .NET Compact Framework developers.

When I was looking into implementing a GAC installed of the OpenNETCF assemblies for the Smart Device Framework, I ultimately took a different approach to versioning. The reason for this is I didn't want to have a bunch of assemblies with the same significant version signature (major.minor.build) in GAC. Instead, I opted to use a fixed AssemblyVersion and for our internal version tracking we would use the Win32 File Version number and increment this on each build.

Of course, using the fact that the revision field is insignificant in version binding, it means we can easily drop hot fixes and revisions into the GAC as and when we see fit. That said, we've not had the need to that so far.

Using the POOM IDL

Windows Mobile Team Blog — Fri, 06 Aug 2004 21:38:00 GMT

.NET CF Versioning

Mikel Berger — Thu, 06 Jan 2005 07:11:00 GMT

More reading for CPT 355 deployment lectures. http://weblogs.asp.net/stevenpr/archive/2005/01/05/347353.aspx which is a Part 2 to this post http://blogs.msdn.com/stevenpr/archive/2004/06/30/170289.aspx...