Bağlantıları görmek için lütfen
Giriş Yap
How often do you see code like this to create a file path?
C#:
public string GetFullPath(string fileName)
{
string folder = ConfigurationManager.AppSettings["somefolder"];
return folder + fileName;
}Code like this drives me crazy because it is so prone to error. For example, when you set the folder setting, you have to remember to make sure it ends with a slash. Having too many things to remember makes this setup fragile.
Sure, you write some code to ensure that the folder has an ending slash, but I’d rather let someone write that code. For example, Microsoft.
The .NET framework is definitely huge so it can be understandable to miss out on some of the useful utility classes in there that will make your life as a developer easier.
C#:
public string GetFullPath(string filename)
{
string folder = ConfigurationManager.AppSettings["somefolder"];
return System.IO.Path.Combine(folder, filename);
}The Path class is certainly well known and probably well used, but is still one of those classes that developers seem to never use to its full potential. For example, how often do you see this?
//make sure folder path ends with slash
C#:
string folder = GetFolderPath() + @"\";Well that’s nice for Windows machines, but our world is changing and someday, you may want your code to run on Linux or, god forbid, a Mac! Instead, you could use this and be safe.
C#:
string folder = GetFolderPath() + Path.DirectorySeparatorChar;That’ll make sure the slash leans in the correct direction based on the platform. Oh, and the next time I see code to parse a file name from a path, I’m going to slap the developer upside the head and mention this method:
C#:
string fileName = Path.GetFileName(fullPath);
Bağlantıları görmek için lütfen
Giriş Yap
This class contains a wealth of information about the current environment in which your code is executing. You can get access to the MachineName, the CommandLine, etc…
However, the one property I would like to get developers to use is a simple one:
C#:
//Instead of this
string s = "Blah\r\n";
//do this
string s = "Blah" + Environment.NewLine;Again, this falls under the case that your code might actually run on a different operating system someday. Might as well acquire good habits now.
