Licensing .NET components

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

What is the best approach in implemetation of licensing for .NET components? Does .NET include "build in" support for licensing? Or the best way is to look for third party solution like XHEO Licensing product? Does somebody here use XHEO Licensing, if yes could you provide feedback? Can you recommend other licensing products for .NET?
 
..NET has a LicenseProvider class that can be extended if you put a lot of
work into it. It has quirks though, and only works for objects that inherit
from System.ComponentModel. You might look at Desaware's licensing system
(www.desaware.com) - it can use the LicenseProvider, or not (and I think
it's easier if you don't). It's easy to use and has good flexibility and
security.
Make Harsh wrote a licensing article for Windows forms www.windowsforms.net
look under the licensing articles.

Good luck

J


Ottadev said:
What is the best approach in implemetation of licensing for .NET
Click to expand...
components? Does .NET include "build in" support for licensing? Or the best
way is to look for third party solution like XHEO Licensing product? Does
somebody here use XHEO Licensing, if yes could you provide feedback? Can you
recommend other licensing products for .NET?
 
CryptoLicensing - it supports licensing of components and controls. It has a special LicenseProvider derived class and it supports separate design time and run-time licenses.
 
Back
Top