Activity overview
Latest activity by jnsn
Embedding the plug-in is not an option, indeed. These are sold separately or made specially on a customer request base.
Embedding the required assemblies in my plug-in has been an idea, but I would guess this might not always work. It is possible my main application is updated while my plug-ins are not. As long as one of the referenced assemblies does not contain a breaking change they should still work. I assume that the first assembly using another assembly is responsible for loading them into the application domain. So let's say that the plug-in loads CoreA first, using his embedded version, it is possible that another assembly which requires a new function added to CoreA cannot find that function and this would lead to a whole new set of problems. / comments
Embedding the plug-in is not an option, indeed. These are sold separately or made specially on a customer request base.
Embedding the required assemblies in my plug-in has been an idea, but I would...
Thanks!
As I stated in my email, the main reason I choose to embed assemblies is because some things are quite hard to obfuscate. For example the data model used by several other assemblies contains a lot of public classes and properties. In one of the first releases we simply obfuscated the library without embedding which resulted in some users abusing it and modifying their saved data. After embedding it became hard for them to detect where the assembly was and how to use it.
So if possible I would really like to stick with this approach. / comments
Thanks!
As I stated in my email, the main reason I choose to embed assemblies is because some things are quite hard to obfuscate. For example the data model used by several other assemblies contain...
Oops, it seems that by editing my copy paste I've made a mistake.
The correct error message is:
Could not load file or assembly 'CoreA, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
So the problem is not that CoreA.dll is unable to load PluginA.dll, but PluginA.dll is not able to load CoreA.dll.
I will try to create a sample application later today and send it through. / comments
Oops, it seems that by editing my copy paste I've made a mistake.
The correct error message is:
Could not load file or assembly 'CoreA, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or on...
At runtime loaded assembly cannot find embedded assembly.
I am trying to obfuscate an application which loads libraries from a sub-folder at runtime. The libraries in the sub-folder reference libraries in my main folder which I embed in my main executable...