Sign In
Sign Up
Products
Purchase
Downloads
Demos
Forums
Blogs
Documentation
Corporate
Corporate
About Aspose
Contact Us
Customers
Customer List
Case Studies
Testimonials
Purchase
Purchase Policies
Renewal Policies
Purchase FAQs
Resellers
Reselling Policies
Find a Reseller
Press Center
Company News
Newsletter Archive
Legal
Terms of Use
Copyright Notice
Aspose
>
Corporate
>
Purchase
>
FAQs
>
License Class Conflict
License Class Conflict
This wiki FAQ topic shows how to fix the license class conflict and addresses the answer to the questions posted at
http://www.aspose.com/community/forums/thread/20561/where-to-place-lic-file.aspx
http://www.aspose.com/community/forums/thread/14684/trying-to-install-new-license.aspx
http://www.aspose.com/community/forums/thread/19996/license-conflict.aspx
Each Aspose component includes a License class. More info please check
Use License
. But Microsoft .Net Class Library has the same class name:
System.ComponentModel.License
. So in some situation, you will get License class naming conflict. To fix it, please specify the name of the class fully when you use License.SetLicense method. Take
Aspose.Word.License
as an example:
Aspose.Word.License license = new Aspose.Word.License();
The same thing could happen if you are using several Aspose products simultaneously and you have included using directives with appropriate namespaces, for example:
using Aspose.Word;
using Aspose.Pdf;
The solution is the same - use fully qualified name for License.
Contact Us
.
Privacy Policy
.
Terms of Use
.
Site Feedback
© Aspose 2002-2008. All Rights Reserved.