License an asp page

You may copy and distribute the object code form of the following files. You may permit distributors of your programs to copy and distribute the Distributable Code as part of those programs. Distribution Requirements.

For any Distributable Code you distribute, you must. Distribution Restrictions. You may not. An Excluded License is one that requires, as a condition of use, modification or distribution, that. This software will access a list of packages that are supplied by means of an OData service online from Microsoft or a third-party service provider.

Please consult a translator for accuracy if you are relying on the translation or are using this site for official business. Please read the conditions provided before clicking the " I ACCEPT " button which indicates your agreement to abide by those conditions in order to complete transactions online with DRE. Your registration with DRE will confirm your acceptance of and agreement to be bound by the Terms applicable to that access.

You agree to conduct transactions with DRE by electronic means. You are aware that DRE may terminate this agreement at any time. You, as a user of DRE's Internet-enabled transaction services, are responsible for keeping your password secret and confidential and not selecting a password which can be easily determined by others.

Your Liability You agree that use of this Electronic Signature as set forth above is the legal equivalent to your written signed instructions to DRE, and that you will be bound by and liable for all use including unauthorized use by other persons without your knowledge or consent.

You are aware that DRE is under no obligation to confirm the actual identity or authority of any user of the Electronic Signature or any component thereof. Protection of Electronic Signature You, as a user of DRE's Internet-enabled transactions services, agree to keep the Electronic Signature and all components thereof secret and safe to prevent unauthorized use. This includes, but is not limited to: memorizing and keeping safe and private the Username and Password included in the Electronic Signature; avoiding selecting number combinations which may be easy for someone else to guess such as 1, 2, 3, 4 or which are associated with the Licensee such as birth date, or address, and so on; avoiding selecting any part of another password, PIN or code; taking all necessary precautions to ensure that no one finds out any component of the Electronic Signature, including while the Licensee is keying an online transaction.

Verification DRE may, for its protection and without any obligation to you, require verification before accepting any DRE registration logon. DRE has no liability for damages or harm which you may incur or experience as a result of any non-acceptance, delay or restriction in implementing instructions, nor for any unavailability, malfunction, cancellation, restriction or withdrawal of Electronic Update Access or any portion of such service or any device associated with it.

Its feature set is relatively limited in contrast to Microsoft SLP. You get the core licensing capability and that's about it. There are a variety of processes to manage updated dlls and implementing license keys that are far from intuitive and often times don't work.

Desaware has a lot of work to do in this area to increase sales. Many times, the non-informative error messages you'll receive will remind you of Microsoft products. That said Desaware's support is very responsive and quite helpful. They'll give you the specifics you need to resolve the problem and not berate you when like most males you failed to read and follow their directions.

The most common approach with their toolset is to use the client License Manager which uses web services to communicate with the license server to create. NET resource files for inclusion within the assembly you want licensed. NET resource file contains the information your application will need to contact the license server or how to manage non-internet based licensing scenarios. NET source code samples to write code in your assemblies to handle the license validation and execution tasks anyway you like.

Wherever applicable, your app can validate the license against this local external license file. So, your ASP. NET installer or the application itself can get around pretty much any reasonable security restriction you can envision.

At the end of the day, I ended up with a licensing solution that was powerful and flexible along with solid customer support. I got neither from Microsoft SLP. I'd strongly recommend looking at Desaware when deciding on your licensing solution.