Properties and Fields
SQL Server User Group Austria

Whidbey GAC & 64 bit

With Whidbey the directory structure of the global assembly cache changed. Using the Alpha version of Whidbey I cannot see the shared assemblies by opening the explorer to look at <windir>\assembly (using Windows XP). Of course it is possible to use the .NET 2.0 Framework Configuration utility to display these assemblies.

The reason for this is that the directory structure changed. The 1.0/1.1 shared assemblies are in the directory <windir>\assembly\GAC. The .NET 2.0 command line utility gacutil installs the shared assemblies into the directory <windir>\assembly\GAC_Neutral. Besides the directory GAC_Neutral there is a directory GAC_32 that keeps custom marshaler and Microsoft.VisualC assemblies.

I think the reason for this is the 64 bit version of .NET. Specific 64-bit assemblies (marshaling) will be in the GAC_64 directory, and the GAC_Neutral directory is for assemblies that are the same for both 32 and 64 bit versions.

This is a great feature of .NET: moving to 64 bit no changes are needed!
I remember a lot of hard work moving 16-bit applications to 32 bit!

Update: with the March Community Preview the directory GAC_Neutral changed to GAC_MSIL.

Christian

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Sam Gentile's Blog

AUTHOR: Sam Gentile's Blog
IP: 000.000.000.000
DATE: 02/06/2004 09:00:00 AM

Sam Gentile's Blog

AUTHOR: Sam Gentile's Blog
IP: 000.000.000.000
DATE: 03/12/2004 08:42:00 AM

Joshua Flanagan

AUTHOR: Joshua Flanagan
IP: 000.000.000.000
DATE: 03/22/2004 10:56:00 PM

Christian

GAC_Neutral was only used before Beta 1. Thanks for your information about the probing changes for native images.

The comments to this entry are closed.