Rank: Newbie
Groups: Member
Joined: 8/14/2008
Posts: 3
|
Greetings,
We are researching whether to buy the EO controls, and I have a question on how licensing is handled if the component is installed to the GAC.
In general, it sounds like the standard procedure is to deploy the EO DLL in the website bin directory, along with the license file. However, for our deployment, we are going to have several different sites on the same server using the control, so we want to put it in the GAC to keep the deployment dependencies for each site to a minimum. However, if do that, will we still have to put the license file in each of the websites, or can that be stored in some central location as well?
Thanks,
Mike Mooney
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,193
|
Hi Mike,
Our license scheme is not in anyway related to GAC. Placing our DLL into GAC will eliminate the need to include the DLL in the application bin directory, but it does not eliminate the need to use a license file.
You can however eliminate the need to use a license by setting license through code. We support two ways of setting license information:
1. Place the license file in the application's bin directory or on the root directory;
2. Call EO.Web.Runtime.AddLicense in your code. Once you place an order, you will have access to the license code page, that page will generate the necessary calls for you in C# and VB.NET. You can then copy the code directory into your application. When you use this way to set license information, you no longer need to use a license file;
Please let us know if that addresses your concerns. We do understand that centralized license management can be useful. So if you still have any questions/feedback on that, we will be very happy to hear that and we will do our best to accommodate your needs. One possible solution would be add support to read license information from registry. That should allow you to set license key once and for all.
Thanks!
|