Comments
Sort by recent activity
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? / comments
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 SmartAsse...
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). [image] And here is the email that I receive. [image] / comments
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 ...
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. / comments
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 l...
Stephen,
Thanks for the update.
Brandon / comments
Stephen,
Thanks for the update.
Brandon
Another thought might be to provide a way to select a range of dates to view error reports (based on received/generated date). / comments
Another thought might be to provide a way to select a range of dates to view error reports (based on received/generated date).
Jessica,
If possible, I would also like a way to configure the number of reports that are shown (including the option to view all error reports), not just the most recently sent or recently inserted. In our case, after we fix a reported issue, we sometimes additional error reports with the same exception, message and stack trace, but from a different underlying cause. Viewing the error reports by category allows us to find earlier reports and see if they are the same issue, or a different one. But if SmartAssembly only shows up to 500 reports, this view won't always show us those older reports.
Thanks,
Brandon / comments
Jessica,
If possible, I would also like a way to configure the number of reports that are shown (including the option to view all error reports), not just the most recently sent or recently inserte...
Jessica,
Thanks for the tip about the SDK, I have used it for scanning through our error reports to find specific ones, and it's been very helpful.
Brandon / comments
Jessica,
Thanks for the tip about the SDK, I have used it for scanning through our error reports to find specific ones, and it's been very helpful.
Brandon
Simon,
Thanks for the update, I am able to receive email notifications now. / comments
Simon,
Thanks for the update, I am able to receive email notifications now.
There's a command line utility "SmartAssembly.com" you can use. Documentation can be found here: http://documentation.red-gate.com/displ ... line+mode# / comments
There's a command line utility "SmartAssembly.com" you can use. Documentation can be found here: http://documentation.red-gate.com/displ ... line+mode#
Thanks, that took care of my issue quite nicely!
Once other problem I noticed, though. The DLL is signed with a strong name key. I can re-sign it and them embed the result in my main application with no problem. However, if I check "I want to add tamper protection", then I get a SecurityException that the "Assembly has been tampered" when I run the final application. This only happens if the original DLL is not present in the folder containing my executable (for instance, in an installed version). If the DLL I'm embedding is still present in the folder, the SecurityException does not occur.
Note that I can enable the "References Dynamic Proxy" and "I want to use string encoding with improved protection" options with no problem (with or without the original DLL). SmartAssembly indicates that both of these options also add some sort of tamper protection as well. / comments
Thanks, that took care of my issue quite nicely!
Once other problem I noticed, though. The DLL is signed with a strong name key. I can re-sign it and them embed the result in my main application ...