| description |
|---|
Use Checking.FolderExists() |
This analyzer provides the following strings:
| Context | String |
|---|---|
| Error List | Caller uses Directory.Exists instead of Checking.FolderExists() |
| Suggestion Box | Use Checking.FolderExists() instead of Directory.Exists |
| Description | Checking.FolderExists() neutralizes the provided path to its absolute correct path, while Directory.Exists operates at the executable directory (Environment.CurrentDirectory), which may not be what you want. |
This code analyzer detects the usage of Exists from the standard Directory class found in the System.IO namespace.
Using Directory.Exists(), path neutralization doesn't take place to ensure that we have the correct absolute path. This causes some of the filesystem operations to operate on files, which are located in the wrong place, and, therefore, errors throw about a target not being found.
A solution to this problem was made with FolderExists(), because it takes care of the absolute paths and tries to reduce this kind of error caused by passing relative directories to the arguments.
To get a brief insight about how this analyzer works, compare the two code blocks shown to you below:
public static void MyFunction()
{
Directory.Exists("test");
}
public static void MyFunction()
{
Checking.FolderExists("test");
}
You can suppress this suggestion by including it in the appropriate place, whichever is convenient.
For more information about how to suppress any warning issued by the Nitrocid analyzer, visit the below page:
{% embed url="https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/suppress-warnings" %}
We recommend that every caller which use this function use the recommended abovementioned method.