Aspose pdf license

Aspose pdf license DEFAULT

License files are downloaded from our online purchase system.

  1. Go to My Orders and Quotes.
    This page lists your order history with Aspose. In the end of column of the grid next to each order is a Review link.
  2. Click Review for the order you want to download a license for.
    The details for that order are displayed.
  3. At the bottom of the page will be a link titled Download License.
  4. Click Download License at the bottom of the page.
    A dialogue appears to allow you to select where to save the license.

To learn how to set the license, please see the licensing section of the documentation.

Important: you have to be logged in to download. If you have not logged in, or if you log in with an account other than the one that bought the license, you may see a blank order list and not be able to download the license. If you want to change the ownership from the purchaser's account to your account, please refer to how to change ownership of an order by transferring a license.

Sours: https://purchase.aspose.com/

Licensing and Subscription

Sometimes, in order to study the system better, you want to dive into the code as fast as possible. To make this easier, Aspose.Words provides different plans for purchase or offers a Free Trial and a 30-day Temporary License for evaluation.

Note that there are a number of general policies and practices that guide you on how to evaluate, properly license, and purchase our products. You can find them in the “Purchase Policies and FAQ” section.

Free Trial or Temporary License

Aspose.Words is incredible software that developers can try before purchasing.

Free Trial

The evaluation version is the same as the purchased one – the Trial version simply becomes licensed when you add several lines of code to apply the license.

The Trial version of Aspose.Words without the specified license provides full product functionality, but inserts an evaluative watermark at the top of the document upon loading and saving and limits the maximum document size to a few hundred paragraphs.

Temporary License

If you wish to test Aspose.Words without the limitations of the Trial version, you can also request a 30-day Temporary License. For more details, see the “Get a Temporary License” page.

Purchased License

After purchase, you need to apply the license file or include the license file as an embedded resource. This section describes options of how this can be done, and also comments on some common questions.

You need to set the license:

  • only once per application domain

  • before using any other Aspose.Words classes

License Applying Options

Licenses can be applied from various locations:

  • Explicit path
  • The folder containing the Aspose.Words.dll file
  • The folder containing the assembly that called Aspose.Words.dll
  • The folder containing the entry assembly (your .exe)
  • An embedded resource in the assembly is called Aspose.Words.dll
  • As a Metered License – a new licensing mechanism

When you reference Aspose.Words.dll in the application, the library is copied to your output directory (unless Copy Local in the properties for that entry is set to false). Often the easiest way to set a license is to place the license file in the same folder as Aspose.Words.dll and specify just the filename without the path.

Use the SetLicense method to license a component.

Calling SetLicense many times is not harmful, it just wastes processor time.

Apply License Using a File or Stream Object

When developing your application, call SetLicense in your startup code before using Aspose.Words classes.

Load a License from a File

Using the SetLicense method, you can try to find the license file in the embedded resources or assembly folders for further use.

The following code example shows how to initialize a license from a folder:

Load a License from a Stream Object

The following code example shows how to initialize a license from a stream using another SetLicense method:

Include the License File as an Embedded Resource

A neat way to package a license with your application and make sure it will not be lost is to include it as an embedded resource into one of the assemblies that call Aspose.Words. To include a file as an embedded resource, follow these steps:

  1. In Visual Studio, include the .lic file into the project using the “File | Add Existing Item…” menu.
  2. Select the file in the Solution Explorer and set “Build Action to Embedded Resource” in the Properties window.
  3. In your code, invoke SetLicense that passes only the short name of the resource file.

Apply Metered License

Aspose.Words allows developers to apply a metered key. This is a new licensing mechanism.

The new licensing mechanism will be used along with the existing licensing method. Those customers who want to be billed based on the use of API features can use the Metered Licensing.

After completing all the necessary steps to obtain this type of license, you will receive the keys, not the license file. This metered key can be applied using the Metered class specially introduced for this purpose.

The following code example shows how to set metered public and private keys:

Please note that you must have a stable Internet connection for the correct use of the Metered license, since the Metered mechanism requires the constant interaction with our services for correct calculations. For more details, refer to the “Metered Licensing FAQ” section.

Changing the License File Name

The license filename does not have to be “Aspose.Words.LIC”. You can rename it to your liking and use that name when setting a license in your application.

“Cannot find license filename” Exception

When you purchase and download a license, the Aspose website names the license file “Aspose.Words.LIC”. You download the license file using your browser. In this case, some browsers recognize the license file as XML and append the .xml extension to it, so the full file name on your computer becomes “Aspose.Words.lic.XML”.

When Microsoft Windows is configured to hide extensions for known file types (unfortunately, this is the default in most Windows installations), the license file will appear as “Aspose.Words. LIC” in Windows Explorer. You will probably think that this is the real file name and call SetLicense passing it “Aspose.Words.LIC”, but there is no such file, hence the exception.

To solve the problem, rename the file to remove the invisible .xml extension. We also recommend you disable the “hide extensions” option in Microsoft Windows.

Using Multiple Aspose Products

If you use several Aspose products in your application, such as Aspose.Words and Aspose.Cells, here are a few useful tips:

  • Set the License for each Aspose product separately. Even if you have a single license file for all components, for example, “Aspose.Total.lic”, you still need to call SetLicense separately for each Aspose product that you use in your application.
  • Use the Fully Qualified License Class Name. Each Aspose product has a License class in its own namespace. For example, Aspose.Words has Aspose.Words.License and Aspose.Cells has Aspose.Cells.License class. Using the fully qualified class name enables you to avoid confusion as to which license applies to which product.
Sours: https://docs.aspose.com/words/net/licensing/
  1. Guitar lessons greeley
  2. Mac tool franchise income
  3. Axle logistics phone number
  4. Rope lights for bikes
  5. Cod black ops 3
  1. Are Aspose licenses per user, or per named user?
  2. Do we need licensing for only active developers? For example, we have a team of two developers working on shift A and a second team of two developers working on shift B … in this situation do we need two or four licenses?
  3. Do we need a separate license for our Build / CI (Continuous Integration) Server?
  4. I'm a contractor who works with different companies on a project basis. I was licensed for an Aspose product on my last job. Does that mean that I can use it in my next job?
  5. What's the difference between a license and a subscription?
  6. What's the difference between a Small Business and an OEM license?
  7. Where can I find pricing information?
  8. Can two companies temporarily share a license agreement for a period of time?
  9. If my company purchases an Aspose for Java product, can part of the seats be converted to .NET?
  10. What does the term physical location refer to, with regards to licensing?
  11. We have a sizeable development team, but only one person using Aspose products. Do all developers need to be licensed or only the one working directly with the Aspose products?
  12. We have several developers working on a single project, but they are working in a distributed model. Can we still use a site license to properly license our team?
  13. What options do I have do purchase products as a bundle?
  14. Do you support all the features of a specific file format?
  15. There are five of us in the team, but we all work in different offices. What kind of license do we need?
  16. I work in our London offices but the solutions I create for my company are used in our New York and Paris offices. What license do I need?
  17. Can a developer's license be reused if that developer leaves the company or is permanently reassigned to a different project?
  18. A new developer has joined the team, what steps must be taken to transfer the license to the developer's new machine?
  19. Does a working from home (WFH) arrangement change the license type that is required?
  20. How does Metered Licensing work?
  21. How does licensing differ for Android, SharePoint, Reporting Services, JasperReports?
1. Are Aspose developer licenses per user, or per named user?

Aspose Developer licenses are per user, not per named user. We understand that members of a coding team may change over time and that it is not practical to have to update licensing each time that occurs.

2. Do we need licensing for only active developers? For example, we have a team of two developers working on shift A and a second team of two developers working on shift B … in this situation do we need two or four licenses?

All developers who are working on the project need to be licensed. In this situation Aspose sees your team as having four members (even though they work at different times).

3. Do we need a separate license for our build or CI (Continuous Integration) Server?

No, we are happy that customers use Aspose products on one server for solution building purposes at no extra cost. This installation should not be used to circumvent the license terms of your agreement with Aspose and should respect any redistributable or location limitations imposed by your purchased license.

4. I'm a contractor who works with different companies on a project basis. I was licensed for an Aspose product on my last job. Does that mean that I can use it in my next job?

No. Our products are licensed to the organization, not an individual within the organization. Our software are not personal tools that you can move freely from one workplace to another.

If you are working for a company to implement a solution that they will deploy, it is that company's responsibility to ensure that they have licenses for the tools that you need. If you are working as part of their development team, they should buy sufficient licenses to let other members of the team continue maintaining the code when you have left.

On the other hand, if you are self-employed and develop solutions that you sell to other companies, then you should have a Developer OEM License. This allows you to use the product in any number of derived works and deploy them freely.

5. What's the difference between a license and a subscription?

When you buy an Aspose product you get two things: a license and a subscription. The license entitles you to use the software. The subscription entitles you to software updates for a year. The subscription expiry date is stored in the license so when you renew your subscription, you get a new license file.

6. What's the difference between a Small Business and an OEM license?

The number of sites (locations) that the derived work can be used at. An OEM license allows you to use the derived work at any number of sites. This is appropriate when the derived work will be distributed to others outside the organisation, or offered as an online service to any number of people, all in different physical locations. Some licenses allow you to deploy to a specified number of sites:

  • A Developer Small Business license allows your derived works to be used at one location, for example your company's head quarters.
  • A Site Small Business license allows your derived works to be used at up to ten locations, for example your company's head quarters and another nine of your company's offices.

Exactly what a license entitles you to depends on the platform: .NET and Java licenses give you slightly different rights from SharePoint and Android licenses, for example. Read about License Types to find out more.  

7. Where can I find pricing information?

Head to the pricing information page for further details.

8. Can two companies temporarily share a license agreement for a period of time?

Aspose will not agree to licensing more than one company under a single order. Aspose’s products are licensed by the number of developers and deployment locations, to single entities. However, Aspose does offer temporary licenses which can be used in these cases. Click here to learn how to obtain a temporary license.

9. If my company purchases an Aspose for Java product, can part of the seats be converted to .NET?

No. Aspose products are licensed are per platform. If multiple platforms need to be supported, then Aspose offers a “Product Family” suite which licenses all platforms. 

10. What does the term "physical site" or "physical location" refer to, with regards to licensing?

Often times we are asked what the term “physical site” or “physical location” applies to in terms of licensing. A physical location is any office or building with it's own postal address. So if you have several different buildings each with it's own postal address you would need to purchase a separate license for each location (which will be utilizing the product).


How do you classify off-site servers?
If your business has off-site hardware, such as: build machines, backup servers, disaster recovery servers, co-location servers or test servers then you will need to purchase an additional license for each off-site location. A location can include an unlimited number of servers, that still counts as just one location in terms of licensing.

11. We have a sizeable development team, but only one person using Aspose products. Do all developers need to be licensed or only the one working directly with the Aspose products?

All developers who are working on the project that uses Aspose products need to be licensed, even if they do not directly use the Aspose products.

12. We have several developers working on a single project, but they are working in a distributed model. Can we still use a site license to properly license our team?

Yes, a Site license can cover a distributed team as long as the size of the team does not exceed the maximum user count.

13. Do you offer a product bundles?

Yes, you can purchase a product family package for which includes every platform for that product. This is useful if your organisation uses several different technologies and is discounted for the number of products it contains.

In addition there is the Aspose.Total product suite which includes all products for a particular platform e.g .NET or Java. If you are using three or more Aspose products then cost-wise it becomes cheaper to buy Aspose.Total instead of each product individually.

Finally there is a Product Family for Aspose.Total which includes everything, all products for all supported platforms. This is massive value for a great price.

14. Do you support all features of a file format or document manipulation feature?

While Aspose products are extremely powerful we cannot guarantee that every feature is available. If you find a missing feature or a bug please report it on the support forums and it will be communicated to our development team to fix. For mission critical issues consider purchasing paid support for increase priority.

15. There are five of us in the team, but we all work in different offices. What kind of license do we need?

That depends in in part on where you intend to use the derived works (the applications you use Aspose products to create). We recognize that a team can be distributed and allow that in our license structure. In this case, you have a team of five. Whether they are in the same physical location or not, you need enough licenses to cover five developers. They also need to cover the number of locations that the derived work will be used. Here are some scenarios:

  • Scenario 1: The team is distributed over five offices and the derived works will be deployed to and used in the same five offices. You should buy either five Developer Small Business licenses (we offer discounts for multiple licenses) or one Site Small Business. The latter will allow your team to grow the team to up to 10 developers, and the derived work to be used in up to 10 locations.
  • Scenario 2: The team is distributed over five offices and the derived works will be accessed by an unknown number of customers online. You should buy five Developer OEM licenses (we offer discounts for multiple licenses) or one Site OEM license. The latter allows you to grow the team up to 10 developers.
  • Scenario 3: The team is distributed over five offices and the derived works will be accessed by staff in six company offices. You should buy a Site Small Business. This allows you to deploy the the derived works in up to 10 sites. It also allows you to grow the team up to 10 developers.
16. I work in our London offices but the solutions I create for my company are used in our New York and Paris offices. What license do I need?

 That depends on how many physical offices are in New York and Paris. Here are a couple of scenarios:

  • Scenario 1: You are the only developer working with Aspose products. Your derived works are used in one office in New York and one in Paris. One developer, two sites - you need two Developer Small Business licenses.
  • Scenario 2: You are the only developer working with Aspose products. Your derived works are used in six offices in New York (housed in six separate buildings) and seven offices in Paris. One developer, more than ten sites - you need one Developer OEM license.
17. Can a developer's license be reused if that developer leaves the company or is permanently reassigned to a different project?

Yes. If the developer permanently leaves the team and will no longer be working with Aspose products then their license can be transferred to a different developer. See the next question for details about that process.

18. A new developer has joined the team, what steps must be taken to transfer the license to the developer's new machine?

Aspose licenses are not tied to a particular machine or account so the license file can be copied and installed to a new machine provided that any redistributable or location limitations imposed by your purchased license are still respected.

19. Does a working from home (WFH) arrangement change the license type that is required?

We require that each location (distinct building) that the derived work (the application you create with Aspose) is deployed to, or accessed from is licensed. Each location regardless of the type (office, home etc) counts towards the total number of locations to be licensed. In a working from home arrangement your derived work will be accessed remotely from many locations which is considered a multi-site intranet and is not supported by the Developer Small Business license. This applies even if the application is accessed in the office from home via remote desktop, as where the user is physically located is what's counted. If you purchased this license before a working from home arrangement was in place then you will need to upgrade to a Site Small Business license as soon as possible.

A Site Small Business license covers up to 10 locations and supports multi-site intranet so this is the correct minimal license to purchase for a working from home arrangement. If the total number of locations to be licensed does not exceed this number then the one license is all that's required. If you have more than 10 locations then you are required to purchase a second Site Small Business license to cover the additional locations or a move to an OEM license type which covers unlimited locations.

This scenario does not affect Developer OEM or Site OEM licenses as those licenses already cover unlimited locations.

21. How does licensing differ for Android, SharePoint, Reporting Services, JasperReports?

The .NET and Java licenses are concerned with the number of developers and the number of locations to which any derived works (products created with the APIs) are used in. A location can be an office, for example, or any building with its own postal address.

The Android licenses work a little differently. They look to how many apps are created, as well as how many places they are deployed to. There are two options for the latter: Enterprise deployment (for use in one company only) or OEM (unlimited deployment to unlimited companies). An OEM license is used if you are selling the app on a marketplace. A Developer license lets you develop one app and a Site license lets you create up to ten.

The Exporter licenses (SharePoint, Reporting Services, JasperReports) work differently as well, once a SharePoint component is installed, for example, it's features are available to all users of that SharePoint site. So instead of looking at physical locations, the license limits the number of physical servers that the component can be used on.

Sours: https://purchase.aspose.com/
Create an XML file and convert it into PDF with Aspose.Pdf for .NET

.NET and Java API Licensing

Different companies have different needs. To accommodate companies large and small, we offer a variety of license types.

Aspose .NET and Java licenses are either based on the number of developers and the number of locations (buildings) where the products will be used (Developer and Site licenses) or by your usage of the product calculated monthly (Metered licenses).

DescriptionDeveloper Small BusinessDeveloper OEMSite Small BusinessSite OEMMetered Small BusinessMetered OEM

Developers licensed

Developer: a Developer might be a software developer, a systems administrator, report author or any other person who uses the product. Each developer working with Aspose products needs to be licensed.

1

1

10

10

Use derived work at locations

Location: A Location is the physical location where a derived work is used; each distinct address or office building, within or outside an organization.

Derived work: a software program, site, report builder or any other solution, work or product that incorporates or uses Aspose products.

1

10

For use with web sites/apps

Allows distribution of derived works to public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios.

Allows external distribution

Allows distribution of derived works to third parties (e.g embedded in software sold to others).

Royalty free

Use the license without the need to pay royalties or license fees for each use, per each copy or volume sold.

Use in a development library, API or SDK

If you produce software with an API for other developers to use then this applies to you. Further details

License type

Perpetual: The license to use the product does not expire.

Pay-per-use: Pay royalties for the use of the product every month.

Perpetual

Perpetual

Perpetual

Perpetual

Pay-per-use

Pay-per-use

Updates and hotfixes for one year

A purchase includes a subscription which entitles you to one year of product updates.

When the year has passed you are still licensed to use to the product so your existing applications that use Aspose will continue to function but to download and use further updates to the product you first have to renew your subscription. Learn more

Note: Metered licenses are always up to date.

Can be used to create unlimited applications

There are no limits to the number of applications that you create with Aspose products.

Discount applied to multiple purchases

Purchase multiple licenses and receive a discount. Get a quote

Metered licenses contain in-built discounts as adding extra developers does not increase costs. Learn more

Free technical support

Recieve free technical support before purchase or even if your maintenance subscription has expired.

Note that free support included with a license is different from paid support which is an optional additional purchase. Check out the paid support options

Developer Small Business License
One Developer and One Deployment Location

A Developer Small Business License allows One developer to create an unlimited number of derived works using the product which can be used at only One physical location (distinct address or office building) within your organization. A Developer Small Business License covers One developer and/or One physical location. A license must be purchased for each developer in the development team, or for each physical location the derived works will be used, whichever is the greater.

This license is royalty free. It does not support distribution of derived works to third parties, public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios. Only Unlimited Location Licenses support this form of distribution.

This license does notsupport creating derived works that are used in a development library with an API or SDK, only the Metered License types support API usage. Only the Metered License types support API usage.

Read the License FAQ for answers to your questions and scenarios.

Developer OEM License
One Developer and Unlimited Deployment Locations

A Developer OEM License allows One developer to create an unlimited number of derived works using the product which can be used at an unlimited number of physical locations (distinct address or office building) within or outside of your organization. A Developer OEM License covers One developer working on derived works which use the product functionality, a SaaS or public facing web project will require this license type. A license must be purchased for each developer in the development team.

This license is royalty free. It allows distribution of derived works to third parties, public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios. This license does notsupport creating derived works that are used in a development library with an API or SDK, only the Metered License types support API usage.

Read the License FAQ for answers to your questions and scenarios.

Site Small Business License
Up to Ten Developers and up to Ten Deployment Locations

A Site Small Business License allows Ten developers to create an unlimited number of derived works using the product which can be used at Ten physical locations (distinct address or office building) within your organization. If more than Ten developers use or have access to the product and/or you use the derived works at more than Ten physical locations, buy multiple Site Small Business Licenses or extra Developer Small Business Licenses.

This license is royalty free. It does not support distribution of derived works to third parties, public facing websites/applications, extranets or SaaS project usage scenarios. Only Unlimited Location Licenses support this form of distribution. It can support multi-site intranet usage subject to the restrictions on developers and physical location numbers.

This license does notsupport creating derived works that are used in a development library with an API or SDK, only the Metered License types support API usage. Only the Metered License types support API usage.

Read the License FAQ for answers to your questions and scenarios.

Site OEM License
Up to Ten Developers and Unlimited Deployment Locations

A Site OEM License allows Ten developers to create an unlimited number of derived works using the product which can be used at an unlimited number of physical locations (distinct address or office building) within or outside of your organization. A Site OEM License covers Ten developers working on derived works which use the product functionality. A SaaS or public facing web project will require this license type. If more than Ten developers use or have access to the product buy multiple Site OEM Location Licenses or extra Developer OEM Licenses.

This license is royalty free. It allows distribution of derived works to third parties, public facing websites/applications, extranets, multi-site intranets or SaaS project usage scenarios. This license does notsupport creating derived works that are used in a development library with an API or SDK, only the Metered License types support API usage.

Read the License FAQ for answers to your questions and scenarios.

Metered Small Business License
Unlimited Developers and Deployment Locations, Supports SDK Usage, Pay as you Use

A Metered Small Business license allows an unlimited number of developers from your organisation to create an unlimited number of derived works using the product which can be used at an unlimited number of physical locations (distinct address or office building) within your organization. A Metered Small Business License covers unlimited developers working on derived works which use the product functionality. A SaaS or public facing web project or application with an SDK or API can be used with this license type.

This license type is not royalty free, you pay as you use so your costs will automatically scale with deployment usage. It does support public facing web sites/applications, extranets or SaaS project usage scenarios and creating derived works that are used in a development library with an API or SDK

Read the Metered License FAQ for answers to your questions and scenarios.

Metered OEM License
Unlimited Developers and Deployment Locations, Supports SDK Usage, Pay as you Use

A Metered OEM license allows an unlimited number of developers from your organisation to create an unlimited number of derived works using the product which can be used at an unlimited number of physical locations (distinct address or office building) within or outside of your organization. A Metered OEM License covers unlimited developers working on derived works which use the product functionality. A SaaS or public facing web project or application with an SDK or API can be used with this license type.

This license type is not royalty free, you pay as you use so your costs will automatically scale with deployment usage. It does support public facing web sites/applications, extranets or SaaS project usage scenarios and creating derived works that are used in a development library with an API or SDK

Read the Metered License FAQ for answers to your questions and scenarios.

Sours: https://purchase.aspose.com/

Pdf license aspose

Licensing and limitations

Limitation of an evaluation version

We want our customers to test our components thoroughly before buying so the evaluation version allows you to use it as you would normally.

  • PDF created with an evaluation watermark. The evaluation version of Aspose.PDF for Java provides full product functionality, but all the pages in the generated PDF documents are watermarked with “Evaluation Only. Created with Aspose.PDF. Copyright 2002-2020 Aspose Pty Ltd” at the top.

  • The limit of the number of collection items that can be processed. In the evaluation version from any collection, you can process only four elements (for example, only 4 pages, 4 form fields, etc.).

You can download an evaluation version of Aspose.PDF for Java from Aspose Repository. The evaluation version provides absolutely the same capabilities as the licensed version of the product. Furthermore, evaluation version simply becomes licensed when you purchase a license and add a couple of lines of code to apply the license.

Once you are happy with your evaluation of Aspose.PDF, you can purchase a license at the Aspose website. Make yourself familiar with the different subscription types offered. If you have any questions, do not hesitate to contact the Aspose sales team.

Every Aspose license carries a one-year subscription for free upgrades to any new versions or fixes that come out during this time. Technical support is free and unlimited and provided both to licensed and evaluation users.

If you want to test Aspose.HTML for Java without the evaluation version limitations, you can also request a 30-day Temporary License. Please refer to How to get a Temporary License?

Classic license

The license can be loaded from a file or stream object. The easiest way to set a license is to put the license file in the same folder as the Aspose.PDF.dll file and specify the file name without a path, as shown in the example below.

The license is a plain text XML file that contains details such as the product name, number of developers it is licensed to, subscription expiry date and so on. The file is digitally signed, so do not modify the file; even the inadvertent addition of an extra line break into the file will invalidate it.

You need to set a license before performing any operations with documents. You are only required to set a license once per application or process.

The license can be loaded from a stream or file in the following locations:

  1. Explicit path.
  2. The folder that contains the aspose-pdf-xx.x.jar.

Use the License.setLicense method to license the component. Often the easiest way to set a license is to put the license file in the same folder as Aspose.PDF.jar and specify just the file name without path as shown in the following example:

Starting from Aspose.PDF for Java 4.2.0, you need to call the following code lines to initialize the license.

Loading a license from file

In this example Aspose.PDF will attempt to find the license file in the folder that contain the JARs of your application.

Loading the license from a stream object

The following example shows how to load a license from a stream.

Setting a License Purchased Before 2005/01/22

Aspose.PDF for Java doesn’t support old licenses anymore so please contact our sales team to get new license file.

Validate the License

It is possible to validate if the license has been set properly or not. The Document class has the isLicensed method that will return true if license has been properly set.

Metered License

Aspose.PDF allows developers to apply metered key. It is a new licensing mechanism. The new licensing mechanism will be used along with existing licensing method. Those customers who want to be billed based on the usage of the API features can use the metered licensing. For more details, please refer to Metered Licensing FAQ section.

A new class Metered has been introduced to apply metered key. Following is the sample code demonstrating how to set metered public and private key.

Using Multiple Products from Aspose

If you use multiple Aspose products in your application, for example Aspose.PDF and Aspose.Words, here are a few useful tips.

  • Set the License for each Aspose Product Separately. Even if you have a single license file for all components, for example ‘Aspose.Total.lic’, you still need to call License.SetLicense separately for each Aspose product you are using in your application.
  • Use Fully Qualified License Class Name. Each Aspose product has a License class in its namespace. For example, Aspose.PDF has com.aspose.pdf.License and Aspose.Words has com.aspose.words.License class. Using the fully qualified class name allows you to avoid any confusion about which license is applied to which product.
Sours: https://docs.aspose.com/pdf/java/licensing/
First Application Using Aspose.Pdf for Java

Aspose PDF License

Limitation of an evaluation version

We want our customers to test our components thoroughly before buying so the evaluation version allows you to use it as you would normally.

  • PDF created with an evaluation watermark. The evaluation version of Aspose.PDF for .NET provides full product functionality, but all the pages in the generated PDF documents are watermarked with “Evaluation Only. Created with Aspose.PDF. Copyright 2002-2020 Aspose Pty Ltd” at the top.

  • The limit of the number of collection items that can be processed. In the evaluation version from any collection, you can process only four elements (for example, only 4 pages, 4 form fields, etc.).

If you want to test Aspose.HTML for .NET without the evaluation version limitations, you can also request a 30-day Temporary License. Please refer to How to get a Temporary License?

Classic license

The license can be loaded from a file or stream object. The easiest way to set a license is to put the license file in the same folder as the Aspose.PDF.dll file and specify the file name without a path, as shown in the example below.

If you use any other Aspose for .NET component along with Aspose.PDF for .NET, please specify the namespace for License like Aspose.Pdf.License.

Loading a license from file

The easiest way to apply a license is to put the license file in the same folder as the Aspose.PDF.dll file and specify just the file name without a path.

When you call the SetLicense method, the license name that you pass should be that of your license file. For example, if you change the license file name to “Aspose.PDF.lic.xml” pass that file name to the Pdf.SetLicense(…) method.

Loading the license from a stream object

The following example shows how to load a license from a stream.

Metered License

Aspose.PDF allows developers to apply metered key. It is a new licensing mechanism. The new licensing mechanism will be used along with existing licensing method. Those customers who want to be billed based on the usage of the API features can use the metered licensing. For more details, please refer to Metered Licensing FAQ section.

A new class Metered has been introduced to apply metered key. Following is the sample code demonstrating how to set metered public and private keys.

For more details, please refer to the Metered Licensing FAQ section.

Please note that COM applications that work with Aspose.PDF for .NET should also use the License class.

One point which needs consideration: Please note that the embedded resources are included in assembly the way they are added i.e. if you add text file as an embedded resource in the application and open the resultant EXE in notepad, you will see the exact contents of text file. So when using license file as an embedded resource, anyone can open exe file in some simple text editor and see/extract the contents of embedded license.

Therefore, in order to put an extra layer of security when embedding the license with the application, you can compress/encrypt license and after that, you can embed it into the assembly. Suppose we have Aspose.PDF.lic license file, so let’s make Aspose.PDF.zip with password test and embed this zip file into solution. The following code snippet can be used to initialize the license:

Applying a License Bought Before 2005/01/22

Aspose.PDF for .NET no longer supports the old-style licenses. If you have a license from before 22 January 2005 and you have updated to a more recent version of Aspose.PDF, please contact our Sales team to get a new license file.

Sours: https://docs.aspose.com/pdf/net/licensing/

Similar news:

Provides methods to license the component.

Inheritance Hierarchy

SystemObject
Aspose.PdfLicense

Namespace:Aspose.Pdf
Assembly: Aspose.PDF (in Aspose.PDF.dll) Version: 21.10.0
Syntax

The License type exposes the following members.

Constructors
NameDescription
Public methodLicense

Initializes a new instance of this class.

Properties
NameDescription
Public propertyEmbeddedObsolete.

License number was added as embedded resource.

Methods
See Also
Sours: https://apireference.aspose.com' target='_self


914 915 916 917 918