Andrew. Thanks. I understand what needs to be in the app.xaml.cs file. My problem is that the method is not there. It feels like what I would expect to see if I am not referencing the appropriate assemblies. I’ve referenced the SciChart v22.214.171.12414 nuget package which results in the following assemblies being referenced. SciChart.Charting
SciChart.Drawing. Is there something else that I’m missing? This isn’t an issue of the watermark showing. The chart works great for me. This is simply an issue of the SetRuntimeLicenseKey() method not being there. In fact, there are no methods for this class (at least none that are showing).
That’s why I asked you to download the test app from Github and run it. The method is there, you are missing nothing but perhaps your project is corrupted, wrong version of SciChart, mismatch of version of scichart etc… Hard to tell without seeing what you see, but I can say – it shouldn’t be difficult, it should just work!
The demo app of yours does work. The one difference I can see is that the nuget package your application references results in one item “SciChart” under my “References” folder whereas my project has 4 different assemblies. I don’t know how to proceed.
Our app is using ‘PackageReference’ setting not Packages.config (under tools-> options -> nuget). It should make no difference. Why don’t you try to make a stand alone project that reproduces the issue and send it over to support? I think you might find the problem while you do that. If not, we can take a look & offer advice how to proceed. Best regards,
I’m not having a good day. I can’t even get the support ticket to submit. It’s giving me a message about cross-site forgery. it’s probably because my sample project is 30mb in size, all of which is the NuGet package that was downloaded. The application is a completely empty app with one reference to the SciChart nuget package.
Yes maximum attachment size is 10MB. Unfortunately the support desk is 3rd party and we can’t control the bad error messages (although … we are in the process of upgrading to something sensible!). Delete all the packages, bin, obj and submit – we can restore on our side.
Well, we’ve successfully demonstrated that 20+ years of software development, most of which have been using Visual Studio and .NET since it’s inception, doesn’t stop someone from forgetting to add a constructor to a class. Yep, you found my problem. I’m feeling pretty dumb now. Thanks for your patience. Now, I’m going to go stick my head in the dish washer. :)