Posts tagged with 'licensing'
Build 462 has released. It includes an exciting new interop with web components (beta) and some nice new PDF and ReportViewer features. It also includes a fix for license validation in older versions of chrome.
In addition to all the great new features we introduced in SpreadJS v11, such as charts and more functions support, we’ve also simplified the licensing. In this blog I'll go over runtime licenses, designer licenses, and how to properly use them in your application.
This blog explains how you can use Xuni 2016 v2.5 with the GrapeCity License Manager Visual Studio add in to license your Xamarin solutions.
Our UWP licensing model has been changed. Since 2016 v2 release, each application that uses UWP Edition controls requires a unique license key (either evaluation one or fully licensed key) to be validated at runtime.
Xuni Android includes controls for Android java development. In this blog post I’ll walk you through getting started using Xuni Android from downloading to building an Android app.
Are you evaluating or just getting started using Xuni in a Xamarin.Android app? Start right here with this blog post. I’ll walk you through getting started using Xuni from download to building a Xamarin.Android app.
Finding and fixing errors in the licenses.licx file is one of our most frequent support requests, and with the attached sample, you can now generate your .licx file automatically.
To use ActiveReports, you need to activate a license key on your machine. To make sure that your machine is licensed, go to the Start page and under GrapeCity, run the License Manager. You can also open it from File Explorer on a path like:
This is a question we get quite frequently, to the point where the answer is saved in the Drafts folder of everyone's Outlook, and I wanted to have a reference for everyone to see. We have a Subscription page on the website as well as an FAQ page and both are good reference points in addition to this post.
ActiveReports has been one of the most popular reporting tools right from its initial VB6 days.With each new release it has evolved and therefore it is so popular among report designers. If we talk about the licensing process for the .NET versions for ActiveReports, then the first three versions viz ActiveReports for .NET 1.0, ActiveReports for .NET 2.0, and ActiveReports for .NET 3.0 had the same licensing model. With ActiveReports 6 it was changed and finally further modified with the release of ActiveReports 7. This blog article is dedicated to the first three versions of ActiveReports for .NET. The reason to publish this blog is simple. To provide developers who are still working with legacy ActiveReports for .NET versions, a place to get all the information they require to successfully license their machines. So let start:
Licensing model of VC++ application is different from WinForms applications. Unlike C# and VB.NET, the VS.NET compiler for managed C++ applications does not automatically embed the keys for licensed controls. This blog explains how you can embed license for ComponentOne controls for Winforms.
With the release of ActiveReports 7, a few changes have been made in the Licensing model. Here in this blog lets discuss a few important changes and licensing troubleshooting tips for ActiveReports 6 and ActiveReports 7.
ComponentOne Studios for Silverlight and WinRT XAML are unique in that they use a different licensing mechanism than all other ComponentOne .NET Studios as described here. They’re different because there is no standard licenses.licx file if you’re building Silverlight or Windows Store applications.
So you've downloaded WinForms Edition, installed and entered your license key, and you're ready to tackle some code. Let’s say you want to start using C1Reports…