Skip to content

Commit 1c7946f

Browse files
authored
Update file-path-formats.md
1 parent 2206694 commit 1c7946f

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/standard/io/file-path-formats.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +43,8 @@ You can determine whether a file path is fully qualified (that is, it the path i
4343

4444
The following example illustrates the difference between absolute and relative paths. It assumes that the directory D:\FY2018\ exists, and that you haven't set any curent directory for D:\ from the command prompt before running the example.
4545

46-
[!code-csharp[absolute-and-relative-paths](~/samples/snippets/standard/io/file-names/cs/paths.cs)]
47-
[!code-vb[absolute-and-relative-paths](~/samples/snippets/standard/io/file-names/vb/paths.vb)]
46+
[!code-csharp[absolute-and-relative-paths](../../../samples/snippets/standard/io/file-names/cs/paths.cs)]
47+
[!code-vb[absolute-and-relative-paths](../../../samples/snippets/standard/io/file-names/vb/paths.vb)]
4848

4949
## UNC paths
5050

@@ -98,8 +98,8 @@ DOS device paths are fully qualified by definition. Relative directory segments
9898

9999
The following example illustrates some of the ways in which you can refer to a file when using the APIs in the <xref:System.IO> namespace. The example instantiates a <xref:System.IO.FileInfo> object and uses its <xref:System.IO.FileInfo.Name> and <xref:System.IO.FileInfo.Length> properties to display the filename and the length of the file.
100100

101-
[!code-csharp[referring-to-the-same-file](~/samples/snippets/standard/io/file-names/cs/file-refs.cs)]
102-
[!code-vb[referring-to-the-same-file](~/samples/snippets/standard/io/file-names/vb/file-refs.vb)]
101+
[!code-csharp[referring-to-the-same-file](../../../samples/snippets/standard/io/file-names/cs/file-refs.cs)]
102+
[!code-vb[referring-to-the-same-file](../../../samples/snippets/standard/io/file-names/vb/file-refs.vb)]
103103

104104
## Path normalization
105105

@@ -203,7 +203,7 @@ Directory.Create("TeStDiReCtOrY");
203203
```
204204
creates a directory named TeStDiReCtOrY. If you rename a directory or file to change its case, the directory or file name reflects the case of the string used when you rename it. For example, the following code renames a file named test.txt to Test.txt:
205205

206-
[!code-csharp[case-and-renaming](~/samples/snippets/standard/io/file-names/cs/renaming.cs)]
207-
[!code-vb[case-and-renaming](~/samples/snippets/standard/io/file-names/vb/renaming.vb)]
206+
[!code-csharp[case-and-renaming](../../../samples/snippets/standard/io/file-names/cs/renaming.cs)]
207+
[!code-vb[case-and-renaming](../../../samples/snippets/standard/io/file-names/vb/renaming.vb)]
208208

209209
However, directory and file name comparisons are case-insensitive. If you search for a file named "test.txt", .NET file system APIs ignore case in the comparison. Test.txt, TEST.TXT, test.TXT, and any other combination of upper- and lowercase letters will match "test.txt".

0 commit comments

Comments
 (0)