You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/storage/files/storage-dotnet-how-to-use-files.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,15 +34,15 @@ Azure Files offers several ways for .NET developers to access data and manage re
34
34
| Approach | How it works | When to use |
35
35
| --- | --- | --- |
36
36
| Standard file I/O libraries | Uses OS-level API calls through Azure file shares mounted using SMB or NFS. When you mount a file share using SMB/NFS, you can use file I/O libraries for a programming language or framework, such as `System.IO` for .NET. | You have line-of-business apps with existing code that uses standard file I/O, and you don't want to rewrite code for the app to work with an Azure file share. |
37
-
| FileREST API | Directly calls HTTPS endpoints to interact with data stored in Azure Files. Provides programmatic control over file share resources. The Azure SDK provides the `Azure.Storage.Files.Shares` client library that builds on the FileREST API, allowing you interact with FileREST API operations through familiar .NET programming language paradigms. | You're building value-added cloud services and apps for customers and you want to use advanced features not available through `System.IO`. |
37
+
| FileREST API | Directly calls HTTPS endpoints to interact with data stored in Azure Files. Provides programmatic control over file share resources. The Azure SDK provides the File Shares client library (`Azure.Storage.Files.Shares`) that builds on the FileREST API, allowing you interact with FileREST API operations through familiar .NET programming language paradigms. | You're building value-added cloud services and apps for customers and you want to use advanced features not available through `System.IO`. |
38
38
| Storage resource provider REST API | Uses Azure Resource Manager (ARM) to manage storage accounts and file shares. Calls REST API endpoints for various resource management operations. | Your app or service needs to perform resource management tasks, such as creating, deleting, or updating storage accounts or file shares. |
39
39
40
40
For general information about these approaches, see [Overview of application development with Azure Files](storage-files-developer-overview.md).
41
41
42
42
This article focuses on working with Azure Files resources using the following approaches:
43
43
44
-
-[Work with Azure Files using System.IO](#standard-file-io-libraries): Mount a file share using SMB or NFS and use the `System.IO` namespace to work with files and directories in the share.
45
-
-[Work with Azure Files using Azure.Storage.Files.Shares](#filerest-api): Use the `Azure.Storage.Files.Shares` client library to work with files and directories in a file share using REST.
44
+
-[Work with Azure Files using System.IO](#work-with-azure-files-using-systemio): Mount a file share using SMB or NFS and use the `System.IO` namespace to work with files and directories in the share.
45
+
-[Work with Azure Files using the File Shares client library for .NET](#work-with-azure-files-using-the-file-shares-client-library-for-net): Use the AzureStorage File Shares client library for .NET to work with files and directories in a file share. This client library builds on the FileREST API.
46
46
47
47
To learn about using the Storage resource provider REST API and management libraries, see [Libraries for resource management](storage-files-developer-overview.md#libraries-for-resource-management).
48
48
@@ -93,7 +93,7 @@ If you don't already have a .NET app, create one using Visual Studio or the .NET
93
93
94
94
### Install the package
95
95
96
-
If you plan to interact with Azure Files using the `System.IO` namespace, you don't need to install any additional packages. The `System.IO` namespace is included with the .NET SDK. If you plan to use the `Azure.Storage.Files.Shares` client library, install the package using NuGet.
96
+
If you plan to interact with Azure Files using the `System.IO` namespace, you don't need to install any additional packages. The `System.IO` namespace is included with the .NET SDK. If you plan to use the File Shares client library for .NET, install the package using NuGet.
97
97
98
98
### [Visual Studio](#tab/visual-studio)
99
99
@@ -120,7 +120,7 @@ If you plan to use the `System.IO` namespace, add the following using directive
120
120
using System.IO;
121
121
```
122
122
123
-
If you plan to use the `Azure.Storage.Files.Shares` client library, add the following using directive to the top of your *Program.cs* file:
123
+
If you plan to use the File Shares client library for .NET, add the following using directive to the top of your *Program.cs* file:
## Work with Azure Files using Azure.Storage.Files.Shares
272
+
## Work with Azure Files using the File Shares client library for .NET
273
273
274
-
The FileREST API provides programmatic access to Azure Files. It allows you to call HTTPS endpoints to perform operations on file shares, directories, and files. The FileREST API is designed for high scalability and advanced features that might not be available through native protocols. The Azure SDK provides client libraries, such as `Azure.Storage.Files.Shares`for .NET, that build on the FileREST API.
274
+
The FileREST API provides programmatic access to Azure Files. It allows you to call HTTPS endpoints to perform operations on file shares, directories, and files. The FileREST API is designed for high scalability and advanced features that might not be available through native protocols. The Azure SDK provides client libraries, such as the File Shares client libraryfor .NET, that build on the FileREST API.
275
275
276
276
Consider using the FileREST API and the File Share client library if your application requires:
0 commit comments