Email notification for error report does not list the application

I recently upgraded from SA6 to SA7.  When I get an email notification that an error has been reported from an application processed with SA7 the subject simply states "An error has been reported."  For applications processed with SA6, the subject states "An error has been reported in <Application Name>".

Also, the SA7 email body only contains the generic text:

"An error has been reported, and an exception report has been uploaded by one of your users.
This email is automatically sent to you each time an exception report is uploaded."

The SA6 email body had more details regarding the application name, version, and build date.

Is there a way to set SA7 to use the more detailed email notification for error reports?
Tagged:

Best Answer

  • Russell DRussell D Posts: 1,093 Diamond 3
    Accepted Answer
    Ok, this is due to the way input parameters are added on the command line. SmartAssembly creates a new settings with an old configuration and a new input. Unfortunately, some settings are ignored during this process (like error reporting). Is it possible to not use the input assembly parameter for now?
    Have you visited our Help Centre?

Answers

  • Jessica RJessica R Posts: 1,031 Rose Gold 3
    Hi @dybalabj,

    We are looking into this - please bear with us!

    Jessica Ramos | Product Support Engineer | Redgate Software

    Have you visited our Help Center?


  • This appears to be working properly on the latest release at least:


    And the corresponding email:


    Can you share what you've got set in AER?
    Have you visited our Help Centre?
  • dybalabjdybalabj Posts: 24 Silver 1
    Below are the settings I'm using.  Perhaps it's an issue with using a custom template?

    I'm also executing SmartAssembly from my Visual Studio project as a Post-Build Event, and specifying the error report template on the command line (to ensure the correct relative path is used - I think this was an issue from an earlier version of SmartAssembly).



    And here is the email that I receive.


  • Can you send in a reproduction at all?
    Have you visited our Help Centre?
  • dybalabjdybalabj Posts: 24 Silver 1
    I've attached a simple project to reproduce the error. 

    Click the button on the .NET application to generate a test error.  The attached SA project only adds error reporting to the application.

    It looks like it's a problem when using SmartAssembly.com from the command line.  Processing via the SA GUI works fine.  If I process my assembly from the command line and only specify the /build <project file> option, it works fine.  If I add the /input=<input assembly> option, then the email notification does not include the application name or version details.  In my actual project, my command line also includes the /output and /errorreporttemplate options, but I have not checked to see if those individually cause the problem as well.
  • Thanks for the zip file - I think its clear whats going on now. Bear with me I've raised an internal case.
    Have you visited our Help Centre?
  • dybalabjdybalabj Posts: 24 Silver 1
    In my case, yes I can remove the input assembly parameter (in fact it looks like I only need the /build <project> parameter now).  I think I only had it because when I first started using SmartAssembly a few years ago it only supported absolute paths, so I was using relative paths in my post-build event.

    Out of curiosity, is there a plan to fix this behavior to work like it did in v6?  Or is this an intentional change in v7?
Sign In or Register to comment.