patching .net assemlies (strong name)

  • Thread starter Thread starter cody
  • Start date Start date
C

cody

Is this possible without violating strong name restrictions? If not, what
can be done if a bug is found in an assembly which resides in the GAC and is
used by multiple applications?
Any Ideas?
 
Is this possible without violating strong name restrictions?
Click to expand...

What kind of patching are we talking about?

If not, what
can be done if a bug is found in an assembly which resides in the GAC and is
used by multiple applications?
Click to expand...

Install a new version of the assembly and use publisher policy to
direct clients of the old version to the new.


Mattias
 
Mattias Sjögren said:
What kind of patching are we talking about?



Install a new version of the assembly and use publisher policy to
direct clients of the old version to the new.
Click to expand...

Thats exactly what I was looking for :-)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Shared Assembly in GAC and its dependencies assemblies 18
Problem referencing strong-named assembly in the GAC 1
Installaing assembly in GAC without strong name 1
Type.GetType(), GAC, strong names 1
Any reason NOT to strong-name an assembly? 10
Strongly named assembly won't load 1
Strong Name Assemblies 1
convert a weakly named assembly to a strongly named 3

Back
Top