This project has moved. For the latest updates, please go here.

Current Build Does not get Assemblies correct - keep using Release version

Aug 26, 2009 at 4:58 AM

I think we will have to go back to using "Soft Links" or references in Visual Studio instead of using ILMERGE with multiple assemblies (ExceptionReporter.Core/ExceptionReporter.WinForms etc)

IlMerging has some complications for when we need to call Assembly.GetExecutingAssembly(). Basically it won't work as is - and no work around looks acceptable.

So, you might have noticed if you've tried to use the latest checkout, some aspects of ExceptionReporter are not working correctly at the moment.

So it probably goes without saying anyway, the recommendation is to use the last release.

Aug 31, 2009 at 12:26 AM
Edited Aug 31, 2009 at 12:32 AM

I believe this is fixed this, as of ChangeSet 28355

Sep 7, 2009 at 12:48 AM

Infact, as of 28909  I'm using ExceptionReporter in a production environment. So if there's anything wrong, I haven't seen it ;-)