tags:

views:

40

answers:

1

I am writing a custom mvc control (commercial), and all of the control's code lives in the custom htmlhelper code that i will have to distribute to the user.

I am ok with this for my commercial license sale, but for evaluating the controls, if i give out the htmlhelper code locally for my potential customers to evaluate, the user can simply "get" all the code and hence he may never buy it since he's got teh control code.

How do i protect my htmlhelper code while somebody is evaluation my cusotm mvc controls?

Is this a general problem or (I wish) i am missing something here?

Thanks.

A: 

Instead of giving code, you can give assembly and documentation. You can also use obfuscator to make your code less readable. Here you can find some questions about obfuscation: http://stackoverflow.com/search?q=obfuscator+.net. There are some free tools to obfuscate code ( http://stackoverflow.com/questions/2161201/free-net-obfuscator ).

LukLed
Yeah, but i thought these MVC control HtmlHelper code could not be put inside an assembly, and called from your view files. Can they be? then cool :-)
Oats
i.e. i was under the impression that these are client side scripts / code (i.e. my custom mvc control code), and had to be distributed as ..js files so customers can place/reference them in their view (aspx, etc) files.
Oats
@Oats: It surely could, just try.
LukLed
@Oats: If you want to extend `HtmlHelper` class, this is .NET code placed in assembly. It is not JavaScript.
LukLed