How can we help you today? How can we help you today?

What's new

Hi All,

Two questions:

1) Where can I find the new feature list for the first Red-Gate branded {smartassembly} release?

2) Regarding the ability to send exception reports back to developers. This feature is someway in confilct with the new .NET Framework Client Profile (a .NET Framework subset). How will {sa} deal with this? or we need always to reference the full .NET Framework to use this feature in our apps?

Thanks.

Alberto
devdept
0

Comments

6 comments

Sort by
  • Alex D
    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,
    Alex D
    0
  • devdept
    Thanks for the list Alex.

    Regarding client profile, in Visual Studio 2010 is the *default* option for all client applications. I understand your point but it means that all setup tools will check&download only .NET client profile on machine that require it and therefore will invalidate {sa} exception reporting feature...
    devdept
    0
  • Sentinel
    Please note, value of .NET 4 ClientProfile changed singnificaly.

    Please check: http://blogs.msdn.com/jgoldb/archive/20 ... e-rtm.aspx and http://www.hanselman.com/blog/TowardsAS ... ngNET.aspx

    Client Profile is *the* framework that will be available on Windows Update for desktops.

    So by default desktops will have only client versions of 4.0 Framework and SA will force them to setup full version. It really upset :(
    Sentinel
    0
  • devdept
    Yes, this is exactly what I meant...

    Alberto
    devdept
    0
  • Alex D
    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!
    Alex D
    0
  • devdept
    I thought that no web functionality was included, how could SA send the report without these APIs?

    I will investigate further.

    Thanks,

    Alberto
    devdept
    0

Add comment

Please sign in to leave a comment.