0

Is there any downside other than the increased package size, for deploying a DLL that is part of the GAC?

What should we be worried when we do this? I believe GAC DLLs win over local DLL, so worst case scenario, if the target machine does not have the DLL on GAC and the local DLL is for 64 bit but the target machine is 32 bit, I can see a problem. But in this case, deploying the DLL as local copy does not make it worse.

I am not suggesting to put everything on local copy. I am wondering if local copy approach is to be considered as "safer way".

kennethc
  • 814
  • 1
  • 10
  • 26
  • 1
    You are playing a dangerous game. Commit to one or the other. You don't need the DLL Hell when you deploy a local bug fix and it just has no effect because the copy in the GAC is used instead. – Hans Passant Sep 10 '13 at 19:26

1 Answers1

0

There is nothing wrong with it at all. You GAC DLLs will "win" over your local bin if they are the same version number and if they are the same version number there is no problem, a neither here nor there kind of thing. See this question on stack: Dll in both the bin and the gac, which one gets used?

Community
  • 1
  • 1
Brian Ogden
  • 18,439
  • 10
  • 97
  • 176