Email Validator 2.0 supports Visual Studio 2005.
Email Validator 2.0 supports .Net Framework 2.0 whereas Email Validator 1.1 supports .Net Framework 1.x. For Email Validator 2.0 .NET Framework 2.x is Required where as for Email Validator .NET Framework 1.x is Required.
Email Validator 2.0 includes new demo with Sample Code for Windows with Visual Studio 2005. You can test it by downloading it from Download Email Validator 2.0 for windows
Email Validator 2.0 includes new demo with Sample Code for Web with Visual Studio 2005. You can test it by downloading it from Download Email Validator 2.0 for web
Email Validator now has the capability to validate comma separated email addresses.
Validating to the MXRecords, Email Validator returns a successful validation for email address found in Known/Accepted Domains*.
* There are a number of domains that are known to exist, and have a high frequency of being added to your email list. Some of these Known/Accepted domains include "hotmail.com; aol.com; yahoo.com; usa.net; bigfoot.com; ibm.net; earthlink.net; mindspring.com; msn.com; uno.com; ibm.com; excite.com; geocities.com; compuserve.com; altavista.com; microsoft.com; netzero.net".
Email Validator allows you to validate email addresses and MX Records , from any .NET application. Email Validator can be used from ASP.NET web pages, to windows forms, to web services. The only limitation to using Email Validator is your programming imagination.
Email Validation Control first checks syntax of email address before actually checking with SMTP server and mailbox.
By default ASP.Net Email Validator checks your system for your primary DNS server. As a benefit, you can specify specific DNS Servers in the form of a comma-delimited string. ASP.Net Email Validator will attempt to connect to each one, until a successful connection is made, and then use the first responsive DNS Server for the remainder of the ASP.Net Email Validator session.
Email Validator has a built-in high performance internal cache that stores previously looked-up MX Records. For example, once the MX Records for hotmail.com have been determined, Email Validator no longer makes the expensive DNS Queries again, to determine those records. Instead, when the 2nd email address is encountered, that belongs to hotmail.com, Email Validator checks it's internal cache to see if the records are there, and then uses those records. By default the Email Validator cache is set to time out every 15minutes, however, this time can be set by the programmer, to be minutes, hours, or even days!
How many times have you seen the email address 'firstname.lastname@example.org' or 'email@example.com' or 'firstname.lastname@example.org' entered into your address list? While all of these addresses are technically valid, they are probably not too useful to you or your list. Email Validator provides the capability to add these addresses to a 'Bad Address' list, and every time they are encountered, Email automatically fails them.
Detects the browser type of the requesting client and generates the proper HTML code making the rendered code browser independent.
Built-in design-time support like drag-and-drop, toolbox support and property builders.
By using 100% managed code, the ASP.Net Email Address Validator server control takes advantage of the numerous built-in services of the .Net Framework to enhance performance.
Utilizing the ASP.Net Email Address Validator server control allows you to concentrate on the strategic core of your application and not waste time and talent on non-strategic development.
Reduce cost and time to market. 40%-60% of project time is made up of coding and testing. With the ASP.Net Email Address Validator server control, the coding and testing has already been done!