Marking assembly as released

.NET obfuscator and automated error reporting

Moderators: Luke Jefferson, Alex.Davies, melvyn.harbour

Marking assembly as released

Postby Ed » Wed Jun 16, 2010 9:19 pm

I build both debug and release versions on our build server via continuous integration. When we want to release, we take the last good build, test it and then release it.

How do I after the fact MarkAsReleased the build?
OR
Do I MarkAsReleased every build but then how do I delete the the builds that are not required?
_Ed_
Ed
 
Posts: 5
Joined: Wed Jun 16, 2010 8:55 pm

Postby slaphead99 » Thu Jun 17, 2010 12:48 pm

Just a quick suggestion - when you select the build that will be a release version you may wish to use the command line and the /markasreleased switch. You can use this as an automatic post-build step for your release configuration.
slaphead99
 
Posts: 92
Joined: Wed Mar 10, 2010 2:27 pm

Postby Ed » Thu Jun 17, 2010 2:50 pm

I never build a version targeted for a release. Instead, we build a release version on each build. When I have to do a release, I pick the last successful build, run validation tests, and then release it to the customer. At this point I mark our build as retain indefinitely and need to mark the obfuscation as released.

I need to understand how this decryption is managed and be able to see that the decryption information is available. I will hate to be in a position where I am trying to solve a customer problem and cannot decode a stack trace.
Ed
 
Posts: 5
Joined: Wed Jun 16, 2010 8:55 pm

Postby Alex.Davies » Fri Jun 18, 2010 2:57 pm

Personally, I prefer to mark all builds as released, and keep all maps, as storage space is cheap.

Otherwise, you can mark as released afterwards manually, as slaphead99 says, from the command line.

Things which are not marked as released are only deleted if they receive no new reports for 2 weeks, so if you have a relatively high volume of exception reports, and check often enough (I use a scheduled task every day) they usually get kept when they're needed anyway.
Alex
Developer,
Red Gate .NET Tools
Alex.Davies
 
Posts: 335
Joined: Tue Dec 02, 2008 12:23 pm
Location: Cambridge, uk

Postby Paul.Martin » Fri Jun 18, 2010 3:05 pm

Once you are about to send out a release just run the command line version of SmartAssembly (SmartAssembly.com) with the switch /markasrelease and the parameter the path of the assembly you are about to release.
e.g.
SmartAssembly.com /markasrelease MyExeFile.exe

There is more information about the command line version in our support pages.

Note 1:
Information not marked "as release" is deleted if it is not accessed (i.e. exceptions reported) for 15 days. This is configurable, so if you know that it will take longer than 15 days between building your application and marking it for release then you should extend the time. In the SmartAssembly.settings file (which will either be where you have installed SmartAssembly on XP or in "C:\\ProgramData\\Red Gate\\SmartAssembly 5\\" on Vista / Win 7) in the "Options" section change or add a "Maps" node with the attribute ObsoleteAfterNDays="x" where x is the number of days.
e.g.
Code: Select all
<SmartAssembly.Settings>
    ....
    <Options>
        ....
        <Maps ObsoleteAfterNDays="30" />
    </Options>
</SmartAssembly.Settings>



Note 2:
This is only relevant if you are using the Error Reporting feature of SmartAssembly, if you are using the ASCII encoding to use the more traditional Stack Trace Decode feature you don't need to worry about this.
Paul.Martin
 
Posts: 83
Joined: Wed Feb 03, 2010 11:20 am
Location: Cambridgeshire


Return to SmartAssembly 5

Who is online

Users browsing this forum: No registered users and 0 guests