I'm glad to hear that helped!
Regarding this new problem, there is unfortunately a known issue with embedding tamper protected assemblies as you are seeing.
Our tamper protection feature works by hooking into an assembly's static constructors and adding the 'StrongNameSignatureVerificationEx' windows API call to those methods (http://msdn.microsoft.com/en-us/library ... 9(v=vs.100
).aspx). This verification call uses GetExecutingAssembly to find the physical file of the tamper protected asssembly and then verifies that file's signature against the signature in its manifest.
The issue with embedding a tamper protected assembly though is that a physical file for it does not actually exist. Thus, the GetExecutingAssembly call fails and the signature verification ultimately fails as well. (but keeping a copy of the embedded DLL in the folder would prevent this)
I'm afraid that to embed the assembly, you will need to protect it without the "I want to add tamper protection" option enabled :/
Please let me know if you have any further questions on this!