Merge pull request #6578 from MicrosoftDocs/main

Auto Publish – main to live - 2026-03-31 23:04 UTC

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -11379,6 +11379,61 @@
       "source_path": "hub/apps/desktop/visual-studio-templates.md",
       "redirect_url": "/windows/apps/dev-tools/visual-studio",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/quickstart-listing-files-and-folders.md",
+      "redirect_url": "/windows/apps/develop/files/list-files-folders",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/quickstart-reading-and-writing-files.md",
+      "redirect_url": "/windows/apps/develop/files/create-read-write-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/best-practices-for-writing-to-files.md",
+      "redirect_url": "/windows/apps/develop/files/best-practices-writing-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/quickstart-getting-file-properties.md",
+      "redirect_url": "/windows/apps/develop/files/file-properties",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/quickstart-determining-availability-of-microsoft-onedrive-files.md",
+      "redirect_url": "/windows/apps/develop/files/determine-availability-microsoft-onedrive-files",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/quickstart-managing-folders-in-the-music-pictures-and-videos-libraries.md",
+      "redirect_url": "/windows/apps/develop/files/music-pictures-videos-libraries",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/thumbnails.md",
+      "redirect_url": "/windows/apps/develop/files/thumbnails",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/how-to-track-recently-used-files-and-folders.md",
+      "redirect_url": "/windows/apps/develop/files/track-recently-used-files-folders",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/change-tracking-filesystem.md",
+      "redirect_url": "/windows/apps/develop/files/change-tracking-filesystem",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/file-access-permissions.md",
+      "redirect_url": "/windows/apps/develop/files/file-access-permissions",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "uwp/files/fast-file-properties.md",
+      "redirect_url": "/windows/apps/develop/files/fast-file-properties",
+      "redirect_document_id": false
     }
   ]
 }

…s/best-practices-for-writing-to-files.md …op/files/best-practices-writing-files.mduwp/files/best-practices-for-writing-to-files.md renamed to hub/apps/develop/files/best-practices-writing-files.md uwp/files/best-practices-for-writing-to-files.md renamed to hub/apps/develop/files/best-practices-writing-files.md

@@ -3,28 +3,28 @@ title: Track file system changes in the background
 description: Describes how to track changes in files and folders in the background as users move them around the system.
 ms.date: 12/19/2018
 ms.topic: how-to
-keywords: windows 10, uwp
+keywords: windows 10, winui
 ms.localizationpriority: medium
 ---
 
 # Track file system changes in the background
 
 **Important APIs**
 
--   [**StorageLibraryChangeTracker**](/uwp/api/Windows.Storage.StorageLibraryChangeTracker)
--   [**StorageLibraryChangeReader**](/uwp/api/windows.storage.storagelibrarychangereader)
--   [**StorageLibraryChangedTrigger**](/uwp/api/Windows.ApplicationModel.Background.StorageLibraryContentChangedTrigger)
--   [**StorageLibrary**](/uwp/api/windows.storage.storagelibrary)
+-   [StorageLibraryChangeTracker](/uwp/api/Windows.Storage.StorageLibraryChangeTracker)
+-   [StorageLibraryChangeReader](/uwp/api/windows.storage.storagelibrarychangereader)
+-   [StorageLibraryChangedTrigger](/uwp/api/Windows.ApplicationModel.Background.StorageLibraryContentChangedTrigger)
+-   [StorageLibrary](/uwp/api/windows.storage.storagelibrary)
 
-The [**StorageLibraryChangeTracker**](/uwp/api/Windows.Storage.StorageLibraryChangeTracker) class allows apps to track changes in files and folders as users move them around the system. Using the **StorageLibraryChangeTracker** class, an app can track:
+The [StorageLibraryChangeTracker](/uwp/api/Windows.Storage.StorageLibraryChangeTracker) class allows apps to track changes in files and folders as users move them around the system. Using the StorageLibraryChangeTracker class, an app can track:
 
 - File operations including add, delete, modify.
 - Folder operations such as renames and deletes.
 - Files and folders moving on the drive.
 
-Use this guide to learn the programing model for working with the change tracker, view some sample code, and understand the different types of file operations that are tracked by **StorageLibraryChangeTracker**.
+Use this guide to learn the programing model for working with the change tracker, view some sample code, and understand the different types of file operations that are tracked by StorageLibraryChangeTracker.
 
-**StorageLibraryChangeTracker** works for user libraries, or for any folder on the local machine. This includes secondary drives or removable drives but does not include NAS drives or network drives.
+StorageLibraryChangeTracker works for user libraries, or for any folder on the local machine. This includes secondary drives or removable drives but does not include NAS drives or network drives.
 
 ## Using the change tracker
 
@@ -41,7 +41,7 @@ The next sections walk through each of the steps with some code examples. The co
 
 ### Enable the change tracker
 
-The first thing that the app needs to do is to tell the system that it is interested in change tracking a given library. It does this by calling the [**Enable**](/uwp/api/windows.storage.storagelibrarychangetracker.enable) method on the change tracker for the library of interest.
+The first thing that the app needs to do is to tell the system that it is interested in change tracking a given library. It does this by calling the [Enable](/uwp/api/windows.storage.storagelibrarychangetracker.enable) method on the change tracker for the library of interest.
 
 ```csharp
 StorageLibrary videosLib = await StorageLibrary.GetLibraryAsync(KnownLibraryId.Videos);
@@ -51,14 +51,14 @@ videoTracker.Enable();
 
 A few important notes:
 
-- Make sure your app has permission to the correct library in the manifest before creating the [**StorageLibrary**](/uwp/api/windows.storage.storagelibrary) object. See [File Access Permissions](./file-access-permissions.md) for more details.
-- [**Enable**](/uwp/api/windows.storage.storagelibrarychangetracker.enable) is thread safe, will not reset your pointer, and can be called as many times as you like (more on this later).
+- Make sure your app has permission to the correct library in the manifest before creating the [StorageLibrary](/uwp/api/windows.storage.storagelibrary) object. See [File Access Permissions](./file-access-permissions.md) for more details.
+- [Enable](/uwp/api/windows.storage.storagelibrarychangetracker.enable) is thread safe, will not reset your pointer, and can be called as many times as you like (more on this later).
 
 ![Enabling an empty change tracker](images/changetracker-enable.png)
 
 ### Wait for changes
 
-After the change tracker is initialized, it will begin to record all of the operations that occur within a library, even while the app isn’t running. Apps can register to be activated any time there is a change by registering for the [**StorageLibraryChangedTrigger**](/uwp/api/Windows.ApplicationModel.Background.StorageLibraryContentChangedTrigger) event.
+After the change tracker is initialized, it will begin to record all of the operations that occur within a library, even while the app isn’t running. Apps can register to be activated any time there is a change by registering for the [StorageLibraryChangedTrigger](/uwp/api/Windows.ApplicationModel.Background.StorageLibraryContentChangedTrigger) event.
 
 ![Changes being added to the change tracker without the app reading them](images/changetracker-waiting.png)
 
@@ -78,11 +78,11 @@ The app is then responsible for processing the changes into its own experience o
 ![Reading the changes from the change tracker into an app database](images/changetracker-reading.png)
 
 > [!TIP]
-> The second call to enable is to defend against a race condition if the user adds another folder to the library while your app is reading changes. Without the extra call to **Enable** the code will fail with ecSearchFolderScopeViolation (0x80070490) if the user is changing the folders in their library
+> The second call to enable is to defend against a race condition if the user adds another folder to the library while your app is reading changes. Without the extra call to Enable the code will fail with ecSearchFolderScopeViolation (0x80070490) if the user is changing the folders in their library
 
 ### Accept the changes
 
-After the app is done processing the changes, it should tell the system to never show those changes again by calling the [**AcceptChangesAsync**](/uwp/api/windows.storage.storagelibrarychangereader.acceptchangesasync) method.
+After the app is done processing the changes, it should tell the system to never show those changes again by calling the [AcceptChangesAsync](/uwp/api/windows.storage.storagelibrarychangereader.acceptchangesasync) method.
 
 ```csharp
 await changeReader.AcceptChangesAsync();
@@ -92,8 +92,8 @@ await changeReader.AcceptChangesAsync();
 
 The app will now only receive new changes when reading the change tracker in the future.
 
-- If changes have happened between calling [**ReadBatchAsync**](/uwp/api/windows.storage.storagelibrarychangereader.readbatchasync) and [AcceptChangesAsync](/uwp/api/windows.storage.storagelibrarychangereader.acceptchangesasync), the pointer will be only be advanced to the most recent change the app has seen. Those other changes will still be available the next time it calls **ReadBatchAsync**.
-- Not accepting the changes will cause the system to return the same set of changes the next time the app calls **ReadBatchAsync**.
+- If changes have happened between calling [ReadBatchAsync](/uwp/api/windows.storage.storagelibrarychangereader.readbatchasync) and [AcceptChangesAsync](/uwp/api/windows.storage.storagelibrarychangereader.acceptchangesasync), the pointer will be only be advanced to the most recent change the app has seen. Those other changes will still be available the next time it calls ReadBatchAsync.
+- Not accepting the changes will cause the system to return the same set of changes the next time the app calls ReadBatchAsync.
 
 ## Important things to remember
 
@@ -103,24 +103,24 @@ When using the change tracker, there are a few things that you should keep in mi
 
 Although we try to reserve enough space in the change tracker to hold all the operations happening on the system until your app can read them, it is very easy to imagine a scenario where the app doesn’t read the changes before the circular buffer overwrites itself. Especially if the user is restoring data from a backup or syncing a large collection of pictures from their camera phone.
 
-In this case, **ReadBatchAsync** will return the error code [**StorageLibraryChangeType.ChangeTrackingLost**](/uwp/api/windows.storage.storagelibrarychangetype). If your app receives this error code, it means a couple things:
+In this case, ReadBatchAsync will return the error code [StorageLibraryChangeType.ChangeTrackingLost](/uwp/api/windows.storage.storagelibrarychangetype). If your app receives this error code, it means a couple things:
 
 * The buffer has overwritten itself since the last time you looked at it. The best course of action is to recrawl the library, because any information from the tracker will be incomplete.
-* The change tracker will not return any more changes until you call [**Reset**](/uwp/api/windows.storage.storagelibrarychangetracker.reset). After the app calls reset, the pointer will be moved to the most recent change and tracking will resume normally.
+* The change tracker will not return any more changes until you call [Reset](/uwp/api/windows.storage.storagelibrarychangetracker.reset). After the app calls reset, the pointer will be moved to the most recent change and tracking will resume normally.
 
 It should be rare to get these cases, but in scenarios where the user is moving a large number of files around on their disk we don’t want the change tracker to balloon and take up too much storage. This should allow apps to react to massive file system operations while not damaging the customer experience in Windows.
 
 ### Changes to a StorageLibrary
 
-The [**StorageLibrary**](/uwp/api/windows.storage.storagelibrary) class exists as a virtual group of root folders that contain other folders. To reconcile this with a file system change tracker, we made the following choices:
+The [StorageLibrary](/uwp/api/windows.storage.storagelibrary) class exists as a virtual group of root folders that contain other folders. To reconcile this with a file system change tracker, we made the following choices:
 
-- Any changes to descendent of the root library folders will be represented in the change tracker. The root library folders can be found using the [**Folders**](/uwp/api/windows.storage.storagelibrary.folders) property.
-- Adding or removing root folders from a **StorageLibrary** (through [**RequestAddFolderAsync**](/uwp/api/windows.storage.storagelibrary.requestaddfolderasync) and [**RequestRemoveFolderAsync**](/uwp/api/windows.storage.storagelibrary.requestremovefolderasync)) will not create an entry in the change tracker. These changes can be tracked through the [**DefinitionChanged**](/uwp/api/windows.storage.storagelibrary.definitionchanged) event or by enumerating the root folders in the library using the [**Folders**](/uwp/api/windows.storage.storagelibrary.folders) property.
+- Any changes to descendent of the root library folders will be represented in the change tracker. The root library folders can be found using the [Folders](/uwp/api/windows.storage.storagelibrary.folders) property.
+- Adding or removing root folders from a StorageLibrary (through [RequestAddFolderAsync](/uwp/api/windows.storage.storagelibrary.requestaddfolderasync) and [RequestRemoveFolderAsync](/uwp/api/windows.storage.storagelibrary.requestremovefolderasync)) will not create an entry in the change tracker. These changes can be tracked through the [DefinitionChanged](/uwp/api/windows.storage.storagelibrary.definitionchanged) event or by enumerating the root folders in the library using the [Folders](/uwp/api/windows.storage.storagelibrary.folders) property.
 - If a folder with content already in it is added to the library, there will not be a change notification or change tracker entries generated. Any subsequent changes to the descendants of that folder will generate notifications and change tracker entries.
 
 ### Calling the Enable method
 
-Apps should call [**Enable**](/uwp/api/windows.storage.storagelibrarychangetracker.enable) as soon as they start tracking the file system and before every enumeration of the changes. This will ensure that all changes will be captured by the change tracker.  
+Apps should call [Enable](/uwp/api/windows.storage.storagelibrarychangetracker.enable) as soon as they start tracking the file system and before every enumeration of the changes. This will ensure that all changes will be captured by the change tracker.  
 
 ## Putting it together