📉Files - NKS0016
Use Removing.RemoveFile()
Last updated
Use Removing.RemoveFile()
Last updated
This analyzer provides the following strings:
Context | String |
---|---|
This code analyzer detects the usage of Delete
from the standard File
class found in the System.IO
namespace.
Using File.Delete()
, 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 RemoveFile()
, 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:
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:
We recommend that every caller which use this function use the recommended abovementioned method.
Error List
Caller uses File.Delete
instead of Removing.RemoveFile()
Suggestion Box
Use Removing.RemoveFile()
instead of File.Delete
Description
Removing.RemoveFile()
neutralizes the provided path to its absolute correct path, while File.Delete
operates at the executable directory (Environment.CurrentDirectory
), which may not be what you want.