Comments
1 comment
-
Hi Brian,
Thanks for your post!
I'm not certain but I think this issue may be happening if the assembly containing the "unknown type" was a dependency that did not actually have error reporting enabled on it (but may have had obfuscation applied). Just to confirm though, is the unknown type coming from your main protected assembly or indeed from one of its dependencies? If the latter, has it been processed by SmartAssembly?
Add comment
Please sign in to leave a comment.
Has anyone seen this before? Any ideas on how to fix this?
Thanks,
Brian