An Issue with GAC

[Sabarish]

Hi ,

In our application, we are using certains shared .net dlls (developed
in c#) . We have installed these dlls in GAC, so that client
applications (these client application can be in a different path or
even in different directory) applications can use them... Everything
works fine....

However when we rebuild the shared dlls , we need to rebuild the client
applications ( even if we do not change the version number or strong
name).... so that these can be used.... Can any one help me regarding
this

[Mike Powell]

Hi Sabarish,
Have you tried removing all old versions of your assemblies from the GAC?
if not you may need to do so, if you started with a certain version number,
built a new version and afterwards tried setting the version number
manually, you could have a few different versions in the GAC, this is known
as 'side by side execution' basicaly the GAC will store multiple versions of
the same assembly, and your programs will not detect a newer version until
you recompile them. However if you do not need multiple versions of the
resources, you should create a "publisher policy assembly" and place it in
the GAC, this will point your applications to the desired version of the
assembly.WARNIN G: publisher policy assemblies must ONLY be used when you
modify the assembly (to fix bugs) but you do not modify the backwards
compatibility.

Mike Powell
www.ramuseco.com

"Sabarish" <sa*******@nest ec.netwrote in message
news:11******** **************@ v33g2000cwv.goo glegroups.com.. .

Hi ,

In our application, we are using certains shared .net dlls (developed
in c#) . We have installed these dlls in GAC, so that client
applications (these client application can be in a different path or
even in different directory) applications can use them... Everything
works fine....

However when we rebuild the shared dlls , we need to rebuild the client
applications ( even if we do not change the version number or strong
name).... so that these can be used.... Can any one help me regarding
this

[Sabarish]

Hi Mike,

Thanks for info.... I had removed all the previous versions of the
assemblies for GAC and still the error was coming... but as you said,
the applications are not taking the new version until you recompile
them....

Also we had not changed the version number or strong key.... however
one of the shared dLL that we had was a mixed assembly (C++/CLI) ... we
are used that assembly as a bridge between C# and unmanaged VC8... we
had changed the unmanaged c++ dll.... will that be the reason that the
shared mixed DLL is not working ??

Regards
Sabarish

[Mike Powell]

Seems like quite a complex setup, changing the C++ DLL may have something to
do with your problems, but i really don't know, sorry.

Mike Powell
www.ramuseco.com

"Sabarish" <sa*******@nest ec.netwrote in message
news:11******** **************@ 51g2000cwl.goog legroups.com...

Hi Mike,

Thanks for info.... I had removed all the previous versions of the
assemblies for GAC and still the error was coming... but as you said,
the applications are not taking the new version until you recompile
them....

Also we had not changed the version number or strong key.... however
one of the shared dLL that we had was a mixed assembly (C++/CLI) ... we
are used that assembly as a bridge between C# and unmanaged VC8... we
had changed the unmanaged c++ dll.... will that be the reason that the
shared mixed DLL is not working ??

Regards
Sabarish