Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
As covered well in this question, System.Uri is a good choice to reflect my intention for URIs. But what about for email addresses?
It seems not as clear-cut, because MailAddress has extra information in its DisplayName property that is not a great fit.
You don’t have to use the
DisplayNameif you don’t want or need to. TheMailAddresstype ensures that an email address is well formed by throwing an exception in it’s constructor otherwise. I would argue that it is worth usingMailAddressoverStringfor this reason and also because it communicates intent and adds little overhead.