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.WARNING: 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*******@nestec.netwrote in message
news:11**********************@v33g2000cwv.googlegr oups.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