Tag: .NET

Previously in .net 1.0 and 1.1, to send mail from a console application, you could use

using System.Web.Mail

and use a method similar to this:

static void SendMail()
{
MailMessage msg = new MailMessage();

msg.To = “toaddress1@whatever.com,toaddress2@blah.com”;
msg.From = “fromaddress@whatever.com”;
msg.Subject = “My Subject”;
msg.Body = “My Body”;

msg.BodyFormat = MailFormat.Html;

SmtpMail.SmtpServer = “yourmailserveraddressorip”;

SmtpMail.Send(msg);

}

If you then upgrade to .net 2.0, you will get this when building:

warning CS0618: ‘System.Web.Mail.SmtpMail’ is obsolete: ‘The recommended alternative is System.Net.Mail.SmtpClient. http://go.microsoft.com/fwlink/?linkid=14202’

Nice huh, link doesn’t tell you much except the API is obsolete.
The old way still works, but you get a bunch of ugly warnings.
So, to fix that, you need to do this. First remove the using statement for System.Web.Mail, then add and change your mailing method as follows:

using System.Net.Mail;

static void SendMail()
{
MailMessage msg = new MailMessage();

msg.To.Add(“toaddress1@whatever.com,toaddress2@blah.com”);
msg.From = new MailAddress(“fromaddress@whatever.com”);;
msg.Subject = “My Subject”;
msg.Body = “My Body”;

msg.IsBodyHtml = true;

SmtpClient smtpClient = new SmtpClient(“yourmailserveraddressorip”);

smtpClient.Send(msg);

}

As you can see, pretty close but a few subtle differences. No more warnings! 🙂

** Note that if you really want a good SendMail function, you should pass in the parameters and have overloads for options such as HTML mail, etc. Depending
on the app I am making, I’ll just throw up a email method like this, but it’s really the quick and dirty way to do it. **

if you are doing a Response.Redirect, and are seeing this error, try something like this

string url = someUrlWithNewLines;

url.Replace(“nr”, “”)

Response.Redirect(url);

Seems trivial, but I have seen the error crop up many times. Just for kicks I did a Google search on it, and a lot of people are asking about it, but no real answer. So, here it is 🙂

If you are using caching in ASP.net, and when your cache invalidates, you see some really bad performance or race conditions, you probably need to implement object locks.

if you are trying to execute a process in .net and trying to pass in arguments, and seem to not be getting anywhere, in the “start info”, set UseShellExecute = false. Worked for me 🙂

I think the .NET Framework is great. It is great for web and fat client apps, web services, etc. I think the mistake Microsoft made with it, is it isn’t required with the OS. Too many people don’t have it. It isn’t feasible to develop a fat client app with .NET and expect widespread installations. People that don’t have the framework will be put of by the whopping ~23MB size of the install. I think it is just goofy that Microsoft tries to push .NET down our throats (as developers) – everything is .NET this, .NET that – and it is good, it can do a lot. Thing is – if you want to get an application to the masses, you still have to fall back on C/C++ as it will 99.9% run natively.

Instead of making the .NET framework a optional update on Windows Update, I think that if it was a required update, it would make things a lot better in terms of developers wanting to target a larger audience. Microsoft says that Vista will have .NET Framework 2.0 – but it is too late. Too many people have XP (9X even!) that they will probably never switch to Vista.

I think managed code is good. I don’t think I should have to develop in unmanaged code because it is too much of a PITA to get the framework to end user machines.

🙂