If you have been programming for any length of time, you know how important commenting your code is. You comment your code so that you will know how it works if someone, including yourself, has to go back and look at it again later.

One of my pet peeves as a professional developer is that every so often you run across code written by someone else that has not been commented - or is commented very poorly. Non-commented or poorly commented code can be a big hassle for a developer. Suppose you need to fix a bug in someone else's code and this person no longer works with you or your company. If the code is not properly commented then you could spend a lot of time - and time is money - trying to figure out what the code does. Unless you are trying to obfuscate code to make it more difficult for someone to understand, there is really no excuse to not properly comment it. It only takes a few seconds to write a some words about what your code does.

I recently had an issue with Visual Studio and a pound sign, '#', character in a folder name. It turns out that you need to be careful when you name the folders that you put projects in.

Every once in a while you may find yourself needing to write a file to the web server. For instance, I recently had to write an ASP.NET page that would save certain data from an input XML file as a text file on the web server. Thanks to the nifty abilities of C#, saving the new file was a snap. Read on for more...

Here is a simple function that opens a file, reads it in a line at a time, and prints the output to the screen. The nl2br statement in the function will convert the newline characters ("\n" or "\r\n" depending on your OS) to HTML breaks, "<br>".