Re: strong naming?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: "Alvin Bruney [ASP.NET MVP]" <vapor dan a t h u t ma le dut cu m>
Date: Sat, 24 Jan 2009 11:21:28 -0500

Lack of. If it were strong named, it would not be possible to suffer from this. Lack of strong naming means the runtime only has a version and path to load. There may be cached assemblies, gac'd assemblies etc causing problems.

--
Regards,
Alvin Bruney

Auther Plug
OWC Blackbook now on download at www.lulu.com/owc

"Peter" <xdzgor@xxxxxxxxxxx> wrote in message news:O1TPH$vdJHA.4684@xxxxxxxxxxxxxxxxxxxxxxx

Hi

on occasion when I am working with 3rd party libraries I start getting
errors similar to the following:

The file or assembly 'Common.Logging, Version=1.2.0.0, Culture=neutral,
PublicKeyToken=af08829b84f0328e' or one of its dependencies could not
be read. The found assembly's manifest definition does not match the
assembly's reference. (Exception from HRESULT: 0x80131040)

(parts of the message were in Danish, so I have tried to translate to
English).

This sort of error seems to occur when one 3rd party library references
a dll (here "common.logging.dll") and another does as well, but they
reference different "versions" of the dll.

Is this to do with "strong naming" of dlls?

The problem can sometimes be fixed by "assembly redirection" (although
I also have difficulties configuring this).

/Peter

References:
- strong naming?
  - From: Peter

Prev by Date: Re: Logging Application Block - How to modify settings in code?
Next by Date: Find Printer "The Directory Service is currently unavailable"
Previous by thread: strong naming?
Next by thread: Logging Application Block - How to modify settings in code?
Index(es):
- Date
- Thread

Relevant Pages

Re: Calling managed C++ function from C# program
... The type or namespace name 'HIDBootLoaderFORM' could not be ... found (are you missing a using directive or an assembly reference?) ... I was not using a DLL. ... C# assemblies can only reference managed assemblies. ...
(microsoft.public.dotnet.languages.csharp)
Re: Calling managed C++ function from C# program
... The type or namespace name 'HIDBootLoaderFORM' could not be ... found (are you missing a using directive or an assembly reference?) ... I was not using a DLL. ... C# assemblies can only reference managed assemblies. ...
(microsoft.public.dotnet.languages.csharp)
Re: Probably an easy question re: Namespaces
... Why not just create an assembly (dll) with the shared code, ... make as many EXE files reference that assembly? ... > attempting to do is create a "core program" that will also have several ... >> I've never tried using the same namespace in multiple assemblies. ...
(microsoft.public.dotnet.languages.csharp)
Re: Namespace Question
... >i saw that when i changed it to true my dll was copied to the bin folder ... >and only after i set the copylocal property to false and than to true ... >For the Reference Path Issue, ... Look for assemblies in directories specified with the Reference Path ...
(microsoft.public.dotnet.languages.vb)
Re: Namespace Question
... >>i saw that when i changed it to true my dll was copied to the bin folder ... >>the reference by looking in the following locations, ... Look for assemblies in directories specified with the Reference Path ... >> tried to use the GAC but the process to convert dll to be strong name ...
(microsoft.public.dotnet.languages.vb)