Assembly resolver, side by side, versioning...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have read that you can specify only the major/minor numbers (plus token and
culture) to reference a DLL installed in the GAC, and that the resolver will
"upselect" to the dll with the latest build and revision number. Is this
true?

However, when I add references in the compilation section of the web.config
of an ASP.NET app, it can not find the DLL in the GAC unless I give it the
build and revision number. I would rather not do this and just reference the
major and minor for configuration management reasons. What is up here? Is
this becausee the compiler needs the fully qualified path?

Thanks.
 
inetmug said:
I have read that you can specify only the major/minor numbers (plus
token and culture) to reference a DLL installed in the GAC, and that
the resolver will "upselect" to the dll with the latest build and
revision number. Is this true?
Click to expand...

No, if the library has a strong name then .NET will use the entire
version, including build and revision.
However, when I add references in the compilation section of the
web.config of an ASP.NET app, it can not find the DLL in the GAC
unless I give it the build and revision number. I would rather not
do this and just reference the major and minor for configuration
management reasons. What is up here? Is this becausee the compiler
needs the fully qualified path?
Click to expand...

You could use a partial name if you are loading the library through the
framework API LoadWithPartialName, in this situation you can use a
config file setting <qualifuAssembly> to give the full name.

www.grimes.demon.co.uk/workshops/fusWSEight.htm#Example_8_4

Richard
 
Back
Top