Geek Answers Handbook

Preventing the removal of a common dll during wsp removal / rollback

I am working on a bunch of solutions that use a third-party DLL from vendors such as Telerik. We use dll in most of your solutions. But when I remove any solutions, the dll is removed from the assembly. This is a very bad behavior.

I think that even putting the dll in the bin folder will not help. Because I can use multiple solutions in the same web application. In this case, if I delete the solution, it also removes the DLL from the bin folder.

What is the workaround for this ugly issue?

+4
source share
2 answers

It really hurts. You might consider merging third-party DLLs using ilmerge. Additional approaches can be found in Muhimbi's free SharePoint Coding Guide (chapters 8 and 9)

+3
source

One option is not to include third-party DLLs in your individual solutions. Everything that is installed with the solution will be deleted when this solution is uninstalled. You may have a framework solution that installs regular DLLs. Thus, these common DLL files are only deleted when you delete your solution framework. Or you can have one solution installer for each shared DLL if you want more granular control over them.

See also the question about SharePoint.SE: Several solutions using shared dll libraries can lead to chaos when canceling individual solutions

+1
source

More articles:


All Articles