[Imperishable]

I have recently been working on this project which provides an API for any .Net application to impart the licensing feature. I am now releasing this as an open source project so that users may learn and customize this as per their needs.

Introduction

License Manager API provides full set of functionality and customization to impart the licensing feature in any .Net application. The API is highly flexible and the application code can customize the behavior of how the system would work. Make sure you have a look at the sample demo provided with the API to have a feel of how to get started.

The API is well documented and commented. Here is the link to the online documentation: Documentation

And here is the download link: Download

Note: I am open to suggestions and feedback and also willing to provide support for the project. Feel free to contact me for any doubts/questions.

Meanwhile I am working on creating an end-to-end Licensing System (using this API) which would enable your .Net application to have the licensing feature with minimal lines of code. You would also be able to control user's license through an online management admin panel. And yes, this tool will be 100% free :)
But of course, using the API gives you more power and control over your functionality though you may need to write a bit of a code.

[Marwix]

It looks really good so far, keep upp the good work man ^_^

[Imperishable]

It looks really good so far, keep upp the good work man ^_^

Thanks a lot mate, glad you liked it :D

[Ashi]

Man your coding style is good. And I liked the way you've used interfaces and abstract classes. Most people don't know why or where to use them. Nice work :)

[NotYourNormalApproach]

I'll take a look on it as soon as possible. So far it sounds interesting.

[Imperishable]

Man your coding style is good. And I liked the way you've used interfaces and abstract classes. Most people don't know why or where to use them. Nice work :)

Thanks dude, I practice a lot with these things. But I guess someone didn't like my coding and rated my thread 1 star :D

---

I'll take a look on it as soon as possible. So far it sounds interesting.

Thanks buddy. Let me know if you need help with anything.

[ShadowCloud]

Man your coding style is good...

I have personally found that it is on rather rare occasions that I agree with that statement on HF, but after reading a bit of the code, I'm inclined to agree, good work.

I do have some notes/suggestions though, intended purely as constructive criticism :

1. CustomRegistrationField > Add a fieldtype to the fields so we can implement custom validation logic per field type. Possibly a regex validation?
2. LicenseInfo > Add different duration types rather than just a value, so users can specify seconds, minutes, hours, days, weeks, months, years etc.
3. RegisterMachine > The method currently expects a RegistrationInfo object, what I'd like to see extended here is that you can set up different packages which is then incorporated into the registration, so I can set up a one week, 2 week, one month etc package and upon registration the correct package is already entered into the database, the reason I'm going with packages rather than directly looking at licenses is that packages would allow "bundled" sales of more than one product, so essentially I could sell one package with 5 different licenses.

All in all though, really good work. Keep it up ;)

[Imperishable]

I have personally found that it is on rather rare occasions that I agree with that statement on HF, but after reading a bit of the code, I'm inclined to agree, good work.

I do have some notes/suggestions though, intended purely as constructive criticism :

1. CustomRegistrationField > Add a fieldtype to the fields so we can implement custom validation logic per field type. Possibly a regex validation?
2. LicenseInfo > Add different duration types rather than just a value, so users can specify seconds, minutes, hours, days, weeks, months, years etc.
3. RegisterMachine > The method currently expects a RegistrationInfo object, what I'd like to see extended here is that you can set up different packages which is then incorporated into the registration, so I can set up a one week, 2 week, one month etc package and upon registration the correct package is already entered into the database, the reason I'm going with packages rather than directly looking at licenses is that packages would allow "bundled" sales of more than one product, so essentially I could sell one package with 5 different licenses.

All in all though, really good work. Keep it up ;)

Thanks a lot buddy, both for appreciation and suggestions :)

1. Yes it can be done. Only reason I do not want to do it is because in most cases the default provided fields (Name, Email etc) would suffice and hence the need for CustomRegistrationField would be rare. And client can always validate on his own side if necessary, though its a good feature if API provides it.

2. Yes, good suggestion. Timespan might be a good option.

3. Again a nice feature to have. For simplicity I went with the current approach. But definitely, I'll add it as an additional option when I extend the current API.

[Hacktentiel123]

can you re-upload please ?

[Ninja]

can you re-upload please ?

You are better of using Netseal. This is already 2 years old.

[Imperishable]

You are better of using Netseal. This is already 2 years old.

Right. I never got a chance/time to launch the product although I had big plans to make it better and competitive to Netseal.
For now, better use netseal :)