How can we help you today? How can we help you today?
Alex D
Hi Paul, Sorry for taking a while to get back to you. Although it would be rarely used, that seems like a reasonable feature. Unfortunately, we won't have time to put it in for v5, but I've put it in the bug tracking system. Cheers, / comments
Hi Paul, Sorry for taking a while to get back to you. Although it would be rarely used, that seems like a reasonable feature. Unfortunately, we won't have time to put it in for v5, but I've put it ...
0 votes
We hadn't released the custom web service for v5 (they're incompatible). Here it is: http://downloads.red-gate.com/EAP/Smart ... ervice.zip I hope you'll be able to work out how to use it, it's more or less the same as the old one. Cheers, / comments
We hadn't released the custom web service for v5 (they're incompatible). Here it is:http://downloads.red-gate.com/EAP/Smart ... ervice.zip I hope you'll be able to work out how to use it, it's more...
0 votes
I've investigated the .NET 4 client profile as you asked, and it seems to work fine with smartassembly error reporting. Please let me know if you don't find that to be true. I couldn't get the .NET 3.5 client profile to work at all, whether or not I used smartassembly! / comments
I've investigated the .NET 4 client profile as you asked, and it seems to work fine with smartassembly error reporting. Please let me know if you don't find that to be true. I couldn't get the .NET...
0 votes
Hi Alberto, Here is a rough changelist for version 5: - Improved usability throughout - Made exception reporting available in trials - Simplified product editions - Simplified sharing exception reports - Introduced option to keep IL strictly valid when using control flow obfuscation, which means Mono is still supported - Improved viewing of inner exceptions and stack frames outside your code in exception reporting - Support for Silverlight 4 (previous version worked, but had bugs) - Fixed intermittent bug with string encoding with improved protection on x64 - Added ability to save exception reports as a file after automatic reporting fails in default exception handler - Prevent a confused deputy attack on strings encoding - Better handling of renaming assemblies that are merged - Fixed bugs in pruning related p/Invoke calls - Major bugs in highest obfuscation level fixed - Various minor bugs in obfuscation and pruning features fixed - Removed curly braces from file names Regarding the .NET Framework Client profile, I hadn't read about it before. If I have time, I'll have a look to see whether it's easy to make exception reporting support it, but you understand I can't give it very high priority because since Windows Vista, a .net framework has been included with windows, so the client profile is obsolete. Cheers, / comments
Hi Alberto, Here is a rough changelist for version 5: - Improved usability throughout - Made exception reporting available in trials - Simplified product editions - Simplified sharing exception rep...
0 votes