Comments
Sort by recent activity
Yes, it turned out that the problem was that I had configured the Web Service with the Professional Edition licence key used by our build server, rather than using the Developer Edition licence key that people would use to view the reports.
Switching the key has stopped the NullReferenceException from occuring.
Thanks,
Martin / comments
Yes, it turned out that the problem was that I had configured the Web Service with the Professional Edition licence key used by our build server, rather than using the Developer Edition licence key...
Ah - yes, we did try to set that up initially, but it didn't seem to quite work. It's possible we left it in a miscofigured state,
Could you clarify for me exactly what settings we should configure in the web service so that only people using a copy of SmartAssembly with the licence key of either our Professional or Developer edition of SmartAssembly can download the reports?
Thanks for the prompt response,
Martin / comments
Ah - yes, we did try to set that up initially, but it didn't seem to quite work. It's possible we left it in a miscofigured state,
Could you clarify for me exactly what settings we should configur...
Indeed, I had forgotten to configure SmartAssembly with our custom SQL database name and web service URL when I installed it onto a different build server. User error [image]
It might be worth wrapping the exception in a future version of SmartAssembly so an error such as "MDB databases cannot be used calling SmartAssembly from a 64-bit MSBuild process." is printed to the MSBuild log. I'd have probably found the configuration issue a lot quicker if that had been the case, as the message lead me to believe it was a SmartAssembly bug.
Regards,
Martin / comments
Indeed, I had forgotten to configure SmartAssembly with our custom SQL database name and web service URL when I installed it onto a different build server. User error
It might be worth wrapping t...
Ah - I must have something misconfigured somewhere, as SmartAssembly should be pointing at our in-house SQL server database. / comments
Ah - I must have something misconfigured somewhere, as SmartAssembly should be pointing at our in-house SQL server database.
Sorry, forgot to mention I was talking about the [System.Diagnostics.GeneratedCodeAttribute].
Regards,
Martin / comments
Sorry, forgot to mention I was talking about the [System.Diagnostics.GeneratedCodeAttribute].
Regards,
Martin
Thanks Brian.
Martin / comments
Thanks Brian.
Martin
Thanks Brian. I wasn't aware of the change made in .NET 4.0 for the handling of AccessViolationException. I should have maybe done a bit more digging around on MSDN first. I compiled my sandbox app to test this out in VS2010, so it defaulted to .NET 4.0.
Either changing the .NET Framework version, adding the configuration setting it behave as expected.
With .NET 4.0 and without a process-wide change however, the only way I can get SmartAssembly to catch the AccessViolationException is to add the [HandleProcessCorruptedStateExceptions] attribute and then re-throw the exception.
Maybe SmartAssembly could be changed at some point to allow an option for .NET 4.0 assemblies with error reporting added to get the code injected into the assembly to decorate your error handler with the appropriate attribute to allow it to catch such problems if wanted in the .saproj file?
We would certainly find this beneficial as we could report exceptions caused by our native components, and then prevent the user from continuing, giving us enough leeway to report the error, but not allowing the process to continue longer than neccessary with potentially corrupted memory.
Thanks,
Martin / comments
Thanks Brian. I wasn't aware of the change made in .NET 4.0 for the handling of AccessViolationException. I should have maybe done a bit more digging around on MSDN first. I compiled my sandbox ...