namespace DefaultNamespace
{
public class MainClass
{
public static void Main(string[] args)
{
SmtpClient Server = new SmtpClient("arne");
MailMessage Mailer = new MailMessage();
Mailer.From = new MailAddress("arne@arne");
Mailer.To.Add(new MailAddress("arne@arne"));
Mailer.Subject = "Test";
Mailer.Body = "Dette er en test\r\nlinie 2\r\nlinie 3";
Server.Send(Mailer);
}
}
}
It's an OK solution if you're writing for a single client with a
predictable setup (assuming they don't mind this behaviour), but yeah, not
everybody even has a default email client configured now that webmail
accounts are so prolific, so it's pretty much asking for trouble if being
deployed to multiple users.
I personally hate it when clicking a contact link on a website results in
the email client being launched, and I'd like that behaviour even less in
an application.
It's an OK solution if you're writing for a single client with a
predictable setup (assuming they don't mind this behaviour), but yeah, not
everybody even has a default email client configured now that webmail
accounts are so prolific, so it's pretty much asking for trouble if being
deployed to multiple users.
I personally hate it when clicking a contact link on a website results in
the email client being launched, and I'd like that behaviour even less in
an application.
Yes, I've been checking out the graveyard that is usenet after about five
years away. Strange how much it's shrunk. Some hierarchies seem deader
than they were in the early 1990s.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.