The trial version of EmailVerify for .NET (previously known as EmailVerify.NET) is a full-featured version of the component, limited to 30 days of use. That version does not need any license key, so if you are still trying the product you may freely skip this whole section as it contains instructions on how to configure a license key in regular, purchased copies of the component.
Starting from version 4.0, purchased copies of EmailVerify for .NET need a license key (a small sequence of alphanumeric characters) to work properly. Given so, each regular customer will have access to a password-protected area within the Cobisi website, where he can easily obtain the license keys for every purchase he had made (if available).
EmailVerify for .NET, version 5
To have the component use a license key and work correctly, you should call the SetLicenseKey() static (Shared, in VB) method of the LicensingManager class exactly to that value.
The following block of code, for example, shows how you should set the runtime license key of the library:
Please note that the license key must be set before the VerificationEngine class is instantiated or used. Otherwise, an exception is thrown.
EmailVerify.NET version 4
To have the component use a license key and work correctly, you should set the RuntimeLicenseKey static (Shared, in Visual Basic) property of the EmailVerifier class exactly to that value.
The following block of code, for example, sets the RuntimeLicenseKey property to a fake value:
EmailVerifier.RuntimeLicenseKey = "my license key";
EmailVerifier.RuntimeLicenseKey = "my license key"
Please note that the license key must be set before the EmailVerifier class is instantiated or used. Otherwise, an exception is thrown.
Although nothing prevents you from saving your license key within your configuration file, this approach is highly discouraged as everyone who can access your files (such as a deployed Windows Forms application) will have access to the component as a regular customer too. Embedding your runtime license key within your application’s executable will, at least, protect this information from non-technical prying eyes and will (slightly) increase the difficulty for crackers.
Finally, if you are using the component from within an ASP.NET web site, we also suggest you to set the aforementioned property within the Application_Init() static method of your global.asax.
Not what you are looking for?
Please don't hesitate to contact us if you have problems with any of our products or services; technical support is always free of charge, and requests made by registered clients will have higher priority.