Activity overview
Latest activity by james.davies
(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...
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,
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...
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...
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...
Hi,
The removal of custom attributes is not intended behaviour. Does it occur when there are no SA features enabled ? / comments
Hi,
The removal of custom attributes is not intended behaviour. Does it occur when there are no SA features enabled ?
Hi,
Firstly I should say that v6.5 is a re-architecture which is why it's performance is very different to v6.2 (in many cases better, but some cases worse).
SmartAssembly 6.6 is a recently released update and contains bug fixes and some memory improvements. v6.6 is a recommended update for all users of SmartAssembly 6.5. http://www.red-gate.com/supportcenter/C ... rtAssembly
Please give it a try and let me know if there are still performance problems. / comments
Hi,
Firstly I should say that v6.5 is a re-architecture which is why it's performance is very different to v6.2 (in many cases better, but some cases worse).
SmartAssembly 6.6 is a recently releas...
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_...
When you merge and embed dependencies they all end up in the main assembly.
If you want to separately process the DLLs with SmartAssembly , then you need to create a separate SmartAssembly project.
SmartAssembly does not obfuscate public members of DLLs, so that they can still be called from elsewhere. / comments
When you merge and embed dependencies they all end up in the main assembly.
If you want to separately process the DLLs with SmartAssembly , then you need to create a separate SmartAssembly project....
Hi,
Sorry you're having problems with v6.5.
In many cases v6.5 is faster. What features are you using ? Are you merging or embedding large dependencies ?
Can you isolate which SA feature is causing the error in the processed assembly?
(There is a recently fixed bug relating to custom attributes processing which occurs with no features enabled. If that is the case for you , then I can supply a patched version) / comments
Hi,
Sorry you're having problems with v6.5.
In many cases v6.5 is faster. What features are you using ? Are you merging or embedding large dependencies ?
Can you isolate which SA feature is causi...