4

I'm working on a bunch of solutions which uses a third party DLL from vendors like Telerik. We use the dll in most of your solutions. But when i uninstall any of the solutions the dll is getting removed from the assembly. This is a very unfortunate behavior.

I guess even putting the dll in the bin folder wont help it. Because i can use multiple solutions in a same web application. In that case if i remove on solution it is removing the dll from bin folder too.

What is the workaround for this ugly issue?

NLV
  • 21,141
  • 40
  • 118
  • 183

2 Answers2

3

This is indeed painful. You could consider merging 3rd party DLLs in using ilmerge. Additional approaches can be found in Muhimbi's free SharePoint Coding Guidelines (Chapters 8 and 9)

Jeroen Ritmeijer
  • 2,772
  • 3
  • 24
  • 31
  • Now i remember having downloaded the same document few months before. Great doc. Good share. Thanks for your response. – NLV Oct 19 '10 at 13:57
1

One option is not to include the third party DLLs in your individual solutions. Anything that gets installed with a solution will be removed when you uninstall that solution. You can have a 'framework' solution that installs common DLLs. This way, those common DLLs are only removed if you remove your framework solution. Or you could have a single solution installer for each shared DLL if you want more fine-grained control over them.

See also the question on SharePoint.SE: Multiple solutions using shared dlls can cause havoc when individual solutions are retracted

Community
  • 1
  • 1
ngm
  • 7,277
  • 1
  • 53
  • 62