We’ve been using Northwoods.GoWin via the NuGet package, until recently using version 6.1 for an application using .Net Framework 4.8 and then moving to .Net 5, this all went smoothly without any issues in GoDiagram.
However, when updating from .Net5 to .Net 6, we’ve started to see the License nag message in the GoView viewport, even though the GoView.LicenseKey is being set to a valid license code.
Even when upgrading to the 6.2 version of Northwoods.GoWin and requesting a new license, we still see the same watermark message:
Please can you advise on what we can do to resolve this.
And then set the GoView.LicenseKey to a key string generated using the application name “ProtoApp”, then this seems to work fine, there is no watermark.
If I then update the TargetFramework in the project file to be “net6.0-windows”, and build and run, then I see the license nag watermark.
That’s right. GoDiagram 6.2.0.5000 was built with .NET 5. Microsoft has done us the favor of making .NET 6 incompatible with our licensing code that has run for over 10 years. I’m afraid you’ll have to run with .NET 5 until we get a new release out with a bugfix and support for .NET 6.
We are also seeing the same issue with GoXam on .Net 6 as well, perhaps unsurprisingly.
Would you have any idea of a timeframe for getting a bugfix for GoDiagram and GoXam?
We have production code targeting .Net 6 as this is the version slated for long term support by Microsoft. This issue and the same one with GoXam is a release blocker for us.
I’ve sent in a license request, using the link from the License Manager in the Northwoods.GoWin 6.3 NuGet package, but I’m only getting a license key string for version 6.2.