In v11.35.1, OneSpanSign.Sdk.Internal.ApplicationLogger no longer seems to work because the trace compiler constant is missing.
I suspect, but did not validate, this setting went missing during the upgrade to netstandard. The visual studio project type for netstandard doesn't have an obvious way to set this, and it seems to be set by default back in the full .net framework days.
According to Microsoft, there are 2 ways to fix the issue:
- Adding
#define TRACE to OSS SDK code.
- specifying the option
/d:TRACE when compiling OSS SDK code.
I didn't check the code on versions newer than v11.35.1, because those tags aren't available.
In case you're curious what's going on behind the scenes, here is what ApplicationLogger looks like when decompiled, and TRACE is not defined. Notice all the empty methods.
Here is what ApplicationLogger looks like when decompiled, and TRACE is defined. Notice methods arent empty.
Here is the quick and dirty fix I used so I could move forward.
In v11.35.1, OneSpanSign.Sdk.Internal.ApplicationLogger no longer seems to work because the trace compiler constant is missing.
I suspect, but did not validate, this setting went missing during the upgrade to netstandard. The visual studio project type for netstandard doesn't have an obvious way to set this, and it seems to be set by default back in the full .net framework days.
According to Microsoft, there are 2 ways to fix the issue:
#define TRACEto OSS SDK code./d:TRACEwhen compiling OSS SDK code.I didn't check the code on versions newer than v11.35.1, because those tags aren't available.
In case you're curious what's going on behind the scenes, here is what ApplicationLogger looks like when decompiled, and TRACE is not defined. Notice all the empty methods.
Here is what ApplicationLogger looks like when decompiled, and TRACE is defined. Notice methods arent empty.
Here is the quick and dirty fix I used so I could move forward.
