GAC

  • Thread starter Thread starter ohil
  • Start date Start date
O

ohil

For shared assemblies, am I correct in saying you deploye
them into GAC?

Also, can you think of a reason why you would not deploy
shared assemblies in the GAC?
 
In my opinion, the GAC is the ONLY logical place to deploy a shared
assembly, as long is it truly is shared. Even if it's not it still won't do
any harm though. If something happens to the GAC the user has a lot more
problems than a fragmented application installation.
 
fragmented....

Are you saying from a support point of view its easier to
maintain if you dont deploye to the GAC?
 
I'm saying from a logic perspective. If an assembly is shared, deploying it
to the GAC allows there to be only one copy for each application that uses
it. Updating it updates it for all applications. It's not any harder to
support, because you KNOW you deployed it to the GAC.

If it's not shared, it's easier to keep it in the installation directory,
that way you don't clutter the GAC and all of your files are in one place.
 
Back
Top