BoldSignEasily embed eSignatures in your .NET applications. Free sandbox with native SDK available.
Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core
to see if that takes care of this issue.
What do you mean by mixed-mode?
On the target system, are there any old syncfusion dll''s (or policy files) in the GAC, or has the target system ever had previous versions on the Syncfusion libraries installed?
The reason I ask is that for the 3.2.1.0 licensing, the mechanism for license checks is supposed to be the same for both build and target systems. If your app is licensed on your build machine, it should be licensed on the deployment machine as well. The faq that this is not true in your case may suggest that somehow old syncfusion DLLs are being used on the deployment system.
Clay
>Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core
>
>to see if that takes care of this issue.
>
>What do you mean by mixed-mode?
>
>On the target system, are there any old syncfusion dll''s (or policy files) in the GAC, or has the target system ever had previous versions on the Syncfusion libraries installed?
>
>The reason I ask is that for the 3.2.1.0 licensing, the mechanism for license checks is supposed to be the same for both build and target systems. If your app is licensed on your build machine, it should be licensed on the deployment machine as well. The faq that this is not true in your case may suggest that somehow old syncfusion DLLs are being used on the deployment system.
>
>Clay
>
Hi Clay,
By mixed mode, I mean that our app is standard C++ and we wrote this dll to wrap Syncfusion.Calculate so that our app can use it. An example of our situation is described at
http://msdn.microsoft.com/msdnmag/issues/05/04/C/default.aspx.
The Syncfusion dlls (Calculate.dll + Core.dll) that we include in our app are copied from Essential Studio\Assemblies\1.1 on the build machine. But so far, any time we try to make our app use Syncfusion.Calculate on a clean machine, it just fails (we DON''T get the "unable to grant runtime license" dialog).
We can make our app use another calculation engine that we are also evaluating. Plus we can make our app use Syncfusion.Calculate on the machine that has Essential Studio installed. So this does look like a licensing issue.
PS:
(1) There are no previous Syncfusion dlls on the clean machine we are testing with and Essntial Studio was never installed on the machine.
(2) We started with the text you suggested in the licx file and that didn''t work either, but we''ll try it again.
Mike
Syncfusion.Core.Licensing.LicensedComponent, Syncfusion.Core
2) From a command line, run LC.exe to create a license file:
lc /target:mcpp.exe /complist:licenses.licx /i:Syncfusion.Core.DLL
Here mcpp.exe is the name of your exe.
3) Then add the file created in step 2, mcpp.exe.licenses, to your managed C++ application as an embedded resource. In VS.NET, right click the project in the Solution Explorer, and then select Properties->Linker->Input, and then add the newly created licenses file in the entry for Embed Managed Resource File.
When you rebuild your executable, the licenses file will be embedded into it for run-time deployment.