Comments
Sort by recent activity
Hi,
Please try upgrading to v6.6.
The release notes ( http://www.red-gate.com/supportcenter/Content/SmartAssembly/articles/version_6xx_SmartAssembly) explain there has been a bug fixed (where attributes were being removed during processing even with no features used).
If this bug was removing the useLegacyV2RuntimeActivationPolicy attribute then that would explain the problem. / comments
Hi,
Please try upgrading to v6.6.
The release notes ( http://www.red-gate.com/supportcenter/Content/SmartAssembly/articles/version_6xx_SmartAssembly) explain there has been a bug fixed (where attri...
(Have heard from developer regarding this:)
This problem is because the current thread context (which is where the unhandled exception handler gets attached) is completely removed at the end of the Application.Run method.
Please use Form.Show instead of Application.Run - http://social.msdn.microsoft.com/Forums/en-us/winforms/thread/aead5e9a-2e06-4adf-aecc-f45a2a633768 / comments
(Have heard from developer regarding this:)
This problem is because the current thread context (which is where the unhandled exception handler gets attached) is completely removed at the end of the...
Error reporting uses the standard application message loop.
It seems that extra calls to Application.Run() cause a problem with this.
It could be that calls to Application.Run() start a new message loop and SA is hooked into the old one causing the exceptions to not be reported.
Thanks for the reproduction of the problem. I will add this to our bug tracking system and see what the developers say. / comments
Error reporting uses the standard application message loop.
It seems that extra calls to Application.Run() cause a problem with this.
It could be that calls to Application.Run() start a new message...
There are no comments yet from the developers on this bug. I will try to get them to take a look. / comments
There are no comments yet from the developers on this bug. I will try to get them to take a look.
Hi,
Here are some ideas:
It could be a clash between your error handling code and the error handling code inserted by SmartAssembly. Is your code still implementing an unhandled exception handler ?
Or it could be related to multiple app domains. Are you using multiple app domains?
Can you throw some simple exceptions elsewhere in your code ? Are any of these reported correctly ?
Is it possible you are using a build script which uses an older saproj that does not have error reporting turned on. / comments
Hi,
Here are some ideas:
It could be a clash between your error handling code and the error handling code inserted by SmartAssembly. Is your code still implementing an unhandled exception handle...
To solve this problem, you need to upgrade to the web service for SmartAssembly 6. Please see this article for details: http://www.red-gate.com/SupportCenter/Content/SmartAssembly/knowledgebase/sa_err2002 / comments
To solve this problem, you need to upgrade to the web service for SmartAssembly 6. Please see this article for details:http://www.red-gate.com/SupportCenter/Content/SmartAssembly/knowledgebase/sa_...