Activity overview
Latest activity by lukasz
As far as I can tell the problem is not with finding the assembly file, so the MandatoryPath/HintPath approach does not solve it. The path visible in the error message is correct and the DLL does exist there. I've tried specifying it as a mandatory path and the result is the same. SA knows where the assembly file is, but for some reason won't load its contents. Any other workaround suggestions? Any ETA on an update that fixes the problem?
/ comments
As far as I can tell the problem is not with finding the assembly file, so the MandatoryPath/HintPath approach does not solve it. The path visible in the error message is correct and the DLL does e...
Any news? Were you guys able to reproduce? This is extremely urgent for us right now. / comments
Any news? Were you guys able to reproduce? This is extremely urgent for us right now.
I'm getting exactly the same error using SA 8.1.1.4963. Attaching my solution together with SA project file. Can someone at your end look into this? To repro: 1. Build the WPFdotNET6 project in Release mode. 2. Build the SA project -> error.
/ comments
I'm getting exactly the same error using SA 8.1.1.4963. Attaching my solution together with SA project file. Can someone at your end look into this?To repro:1. Build the WPFdotNET6 project in Relea...
.NET 6 WPF project won't build
I know there's no official announcement on .NET 6 support (any news appreciated), but posts in this thread seem to suggest that version 8.1.0.4892 does indeed support it: https://forum.red-gate.com...
Hi Jessica, thanks for your answer. I'm not sure what happened, but it started working all of a sudden. The usage reports are decrypted and displayed correctly and this seems to include reports that wouldn't open the other day. I thought perhaps this had to do with timezone difference between our build server (where SA database is) and where the test build was deployed to (it's a few hours ahead), but right now reports become available as soon as the application is closed. No idea where the initial hiccups came from, the SQLite DB we're using certainly hasn't changed. The other issue is still unresolved though - no consent dialog displayed. I'm trying to use the default dialog. If I go with the "first run" option, the SmartAssemblyReportUsage key is created on startup with value False. The "second run" option first creates the key with value Unknown, then on second run changes it to False. Are you able to give me some details on how showing the consent dialog is actually injected into WPF applications? Our application has a custom startup routine that shows a splash screen and delays main window until app intiialization is complete - I'm wondering if this sort of thing might prevent your consent dialog from showing? / comments
Hi Jessica, thanks for your answer.I'm not sure what happened, but it started working all of a sudden. The usage reports are decrypted and displayed correctly and this seems to include reports that...
Feature Usage - can't open reports
I've enabled the Feature Usage Reporting in my project and it seems the app is producing some reports, but when I try to view them an error pops up in SA, saying the reports can't be imported and i...
CSEs error reporting
Hi,
Since .NET 4.0 Corrupted State Exceptions like AccessViolationException cannot be caught/handled unless explicitly marking the handler method with [HandleProcessCorruptedStateExceptions, Securi...