Comments
3 comments
-
Hi Stephen!
I think I've found an error report that you sent in for this and it's linked to issue SA-1109. I know two causes of this issue:
-If you've given your custom error reporting DLL the same name as one of your main assembly's dependencies
If this is the case, it should help if you just give the error reporting DLL a unique name.
-or-
-If you are attempting to actually embed your custom error reporting DLL
If this is the case, you actually don't need to embed or even reference the DLL at all. To use a custom error reporting DLL, you only need to enable error reporting on your assembly, choose the 'custom template' option, and browse to your template. Just as if you were using the standard template, no further code modification is needed
Hope that helps! -
Hello Jessica,
removing the error reporting assembly from the list of used assemblies did the trick.
A suggestion: The emails being send by your mail service might contain the information given by you as some kind of knowledge base entry.
Thanks and regards
Stephen -
I'm glad to hear that helped! And thank you for the suggestion--I've gone ahead and added this info into the response email for SA-1109 error reports.
Add comment
Please sign in to leave a comment.
Any hint how to fix this? Target is a DLL with custome error handler.
Regards
Stephen