gac and assembly versions

[Steve Landis]

I've got two versions of an assembly in the gac: 1.0.0.0 and 2.0.0.0

I've built two versions of a console app that reference the different
versions of the assemblies, yet they both seem to load version 2.0.0.0.
Both references were set using Copy Local = false.

My expectation was that the .exe using the 1.0.0.0 assembly reference would
load version 1.0.0.0 unless there was a policy file or assemblyBinding info
in a config file, but it is using 2.0.0.0.

Anyone know what point I'm missing here? Thanks.

 

[Steve Landis]

Another bit of information: I'm installing the assemblies into the cache in
Windows explorer by dragging and dropping. I didn't use the gacutil.

 

[Steve Landis]

The ApplicationHistory .ini file has the following that seems indicate that
BOTH assemblies are being loaded?

[PolicyResolutionHistory]
ExecutablePath=C:\Visual Studio
Projects\DotNetClassDemos\DemoConsoleClient\bin\DemoConsoleClient.exe
ApplicationName=DemoConsoleClient.exe
NumResolutions=1
ActivationSnapShot_1=29602492.4027048368
[29602492.4027048368]
RuntimeVersion=v1.1.4322
DemoLibrary/ff39c41e604734f9/NULL/1.0.0.0=29602492.4027048368/DemoLibrary/ff
39c41e604734f9/NULL/1.0.0.0
DemoLibrary/ff39c41e604734f9/NULL/2.0.0.0=29602492.4027048368/DemoLibrary/ff
39c41e604734f9/NULL/2.0.0.0
[29602492.4027048368/DemoLibrary/ff39c41e604734f9/NULL/1.0.0.0]
VerReference=1.0.0.0
VerAppCfg=1.0.0.0
VerPublisherCfg=1.0.0.0
VerAdminCfg=1.0.0.0
[29602492.4027048368/DemoLibrary/ff39c41e604734f9/NULL/2.0.0.0]
VerReference=2.0.0.0
VerAppCfg=2.0.0.0
VerPublisherCfg=2.0.0.0
VerAdminCfg=2.0.0.0

 

[Steve Landis]

Never mind.... my stupid mistake. I was actually outputing the name of the
assembly by loading the assembly with a partial name and it was loading ...
v 2.0. Duh.