G
Guest
Apologies if this seems to be a silly question, but...
.... is there anything that can be done to stop other people from using your
DLLs? For example, if you have a solution with three projects: two
applications and a class library, when the applications compile you end up
with an exe and a dll. Since VB doesn't implement linking so that the dll can
be embedded in the exe, it must be distributed as is. What is to prevent
anyone from coming along, pulling out your dll, and then using its classes
for their own projects with just a smile and a nod?
I have experimented with ILMerge, which appears to link the files, until the
application runs, then attempts at serialization using the dll's classes fail
(whereas the nonmerged dll/exe combo works fine).
Would dotfuscator be useful in this situation?
.... is there anything that can be done to stop other people from using your
DLLs? For example, if you have a solution with three projects: two
applications and a class library, when the applications compile you end up
with an exe and a dll. Since VB doesn't implement linking so that the dll can
be embedded in the exe, it must be distributed as is. What is to prevent
anyone from coming along, pulling out your dll, and then using its classes
for their own projects with just a smile and a nod?
I have experimented with ILMerge, which appears to link the files, until the
application runs, then attempts at serialization using the dll's classes fail
(whereas the nonmerged dll/exe combo works fine).
Would dotfuscator be useful in this situation?