Licence registration is causing integration tests to fail
Hi,
We have some actions that make use of XlsIO.
To test these actions, we have some integration tests in a separate project. We register our Syncfusion licence in both the App.xaml.cs constructor (of the production project) and at the beginning of the integration test in the tests project.
We have noticed that some of the outputs generated by XlsIO are appended with "Created with a trial version of Syncfusion Essential XlsIO", causing our tests to fail. What is the recommended way to register Syncfusion for testing purposes?
Thanks,
Josh
SIGN IN To post a reply.
3 Replies
KK
Konduru Keerthi Konduru Ravichandra Raju
Syncfusion Team
February 18, 2020 05:44 AM UTC
Hi Josh,
Greetings from Syncfusion.
Syncfusion introduced the licensing system from v16.2.0.41 for Syncfusion NuGet packages and evaluation setup. We will validate the license key and include the Evaluation warning watermark in the output documents. However, you can remove this evaluation warning by registering license key in your application.
Our license keys are version and platform specific. So, please generate and register the corresponding platform license key for the required version in your application by referring the below KB article.
Regards,
Keerthi.
JO
Josh
February 19, 2020 06:00 PM UTC
Hi Keerthi,
Yes I have already successfully registered my WPF program with a licence key.
My question is how do I register Syncfusion from unit and integration tests? I try to register at the beginning of the test, but this does not work.
[TestMethod]
public void TestMethod()
{
Syncfusion.Licensing.SyncfusionLicenseProvider.RegisterLicense("my licence key");
// A method in my application which uses Syncfusion XlsIO is called here
}
KK
Konduru Keerthi Konduru Ravichandra Raju
Syncfusion Team
February 20, 2020 09:14 AM UTC
Hi Josh,
Thanks for the update.
For every platform, you should register the license key by following the steps suggested in the below documentation link.
To check the reported issue at our end, please share us the following details. It would be much helpful for us to provide you the solution at the earliest.
- Version of Syncfusion NuGet/Installer you are using.
- Ensure whether the referred Syncfusion assemblies are of same version.
- License key used in the application.
- If possible, share us the sample project with the issue reproduced.
Regards,
Keerthi.
SIGN IN To post a reply.
- 3 Replies
- 2 Participants
-
JO Josh
- Feb 17, 2020 06:21 PM UTC
- Feb 20, 2020 09:14 AM UTC