What are the challenges you face when working across database platforms? Take the survey

Working with shared dlls

David4000David4000 Posts: 4 Bronze 1
edited December 5, 2014 10:22AM in SmartAssembly

Apologies if this has been asked and answered before - I searched and couldn't find.

There's a section in the documentation that briefly touches on the subject of having a shared dll in a project and the side-effects thereof. What I need to understand is the correct procedure for protecting the main assembly, other dlls and the shared dll.

So lets say I have:
SA-Project1: Main Assembly A
SA-Project2: Dll Assembly B
SA-Project3: Shared Dll Assembly C

A references B and C
B references C

To be clear, all my assemblies reference many 3rd-party dlls which will be neither merged, embedded or obfuscated. That is to be expected. Additionally both A and B have their own particular Dlls that will be merged into them. I need them to both reference shared dll C and be able to exchange types declared publically in C.

Can I protect C with obfuscation? How do I then embed it into A and B, which will also be obfuscated afterwards?


David Taylor
Sign In or Register to comment.