Hi

What is the better and secure way to supply licensing info with a .net
framework DLL?
By licensing info I mean what classes and to whom are licensed
PS.: I use VS2005 Net Framework 2.0

thanks in advance

Re: How to supply license information with a library (dll) by Pavel

Pavel
Mon Jul 14 05:27:28 CDT 2008

On Jul 14, 2:04=A0pm, Alexander Smirnov <s_alexande...@list.ru> wrote:

> What is the better and secure way to supply licensing info with a .net
> framework DLL?
> By licensing info I mean what classes and to whom are licensed
> PS.: I use VS2005 Net Framework 2.0

There is no truly "secure" way to do that (it is provably impossible
to devise a secure software-only protection scheme), and "better" is
subjective. However, .NET provides a standard framework for licensing
components and controls. You can read more about it here:

http://msdn.microsoft.com/en-us/library/fe8b1eh9.aspx

The advantage of using this scheme is that it is widely known and
understood by developers who might be buying your products.

Re: How to supply license information with a library (dll) by Alexander

Alexander
Mon Jul 14 06:00:15 CDT 2008

As I understand the solution you have suggested in that link is about
licensing control and components. But the class in my DLL is not
derived from System.Windows.Forms.Control

Re: How to supply license information with a library (dll) by Pavel

Pavel
Mon Jul 14 09:38:51 CDT 2008

On Jul 14, 3:00=A0pm, Alexander Smirnov <s_alexande...@list.ru> wrote:
> As I understand the solution you have suggested in that link is about
> licensing control and components. But the class in my DLL is not
> derived from System.Windows.Forms.Control

You do not have to derive from System.Windows.Form.Control - you can
derive from System.ComponentModel.Component. And you can do that only
for some key class or classes of yours, not the entire object
hierarchy (and it's often a good idea to do that anyway, since
designer support for reusable components never hurts).