Comments
1 comment
-
Hi Amir,
Thanks for your post!
Can I first check--what protection options do you have enabled on the assembly?
You'll likely need to exclude some code from obfuscation, pruning, and/or control flow obfuscation to avoid the error.
For any of these protection options that you have enabled, could you please try disabling them one at a time to determine the one causing this?
Please let me know how you get on!
Add comment
Please sign in to leave a comment.
in unprotected dll every thing work fine.
but when I protect file with smart assembly and sign the assembly with same key.
I got following error:
Got unexpected type of System.Data.SqlClient.SqlConnection instead of a ProfiledConnection