Merge pull request #10285 from Mikejo5000/mikejo-br19

Updated link for Test tools landing page

Author: PRMerger7

docs/deployment/clickonce-and-application-settings.md

@@ -1,8 +1,7 @@
 ---
 title: "ClickOnce and Application Settings | Microsoft Docs"
 description: Learn how application settings files work in a ClickOnce application and how ClickOnce migrates settings when the user upgrades to the next version.
-ms.custom: SEO-VS-2020
-ms.date: "11/04/2016"
+ms.date: "08/03/2022"
 ms.topic: "conceptual"
 dev_langs:
   - "VB"
@@ -26,6 +25,7 @@ Application settings for Windows Forms makes it easy to create, store, and maint
  The information below applies only to the default application settings provider, the <xref:System.Configuration.LocalFileSettingsProvider> class. If you supply a custom provider, that provider will determine how it stores its data and how it upgrades its settings between versions. For more information on application settings providers, see [Application settings architecture](/dotnet/framework/winforms/advanced/application-settings-architecture).
 
 ## Application settings files
+
  Application settings consumes two files: *\<app>.exe.config* and *user.config*, where *app* is the name of your Windows Forms application. *user.config* is created on the client the first time your application stores user-scoped settings. *\<app>.exe.config*, by contrast, will exist prior to deployment if you define default values for settings. Visual Studio will include this file automatically when you use its **Publish** command. If you create your ClickOnce application using *Mage.exe* or *MageUI.exe*, you must make sure this file is included with your application's other files when you populate your application manifest.
 
  In a Windows Forms application not deployed using ClickOnce, an application's *\<app>.exe.config* file is stored in the application directory, while the *user.config* file is stored in the user's **Documents and Settings** folder. In a ClickOnce application, *\<app>.exe.config* lives in the application directory inside of the ClickOnce application cache, and *user.config* lives in the ClickOnce data directory for that application.
@@ -34,7 +34,12 @@ Application settings for Windows Forms makes it easy to create, store, and maint
 
  In a ClickOnce application, the size of the configuration files used by application settings is constrained by the size of the ClickOnce cache. For more information, see [ClickOnce cache overview](../deployment/clickonce-cache-overview.md).
 
+## .NET Core and .NET 5+
+
+Currently, a .NET Core assembly to be published needs to be signed with a strong name key file. If it isn't, `ApplicationSettingsBase.Upgrade` method does not copy settings correctly after a new ClickOnce publish. You can specify use of a strong name in the .NET Core project's properties, under the **Build > Strong naming** option.
+
 ## Version upgrades
+
  Just as each version of a ClickOnce application is isolated from all other versions, the application settings for a ClickOnce application are isolated from the settings for other versions as well. When your user upgrades to a later version of your application, application settings compares most recent (highest-numbered) version's settings against the settings supplied with the updated version and merges the settings into a new set of settings files.
 
  The following table describes how application settings decides which settings to copy.
@@ -49,9 +54,11 @@ Application settings for Windows Forms makes it easy to create, store, and maint
 If you have created your own application settings wrapper class and wish to customize the update logic, you can override the <xref:System.Configuration.ApplicationSettingsBase.Upgrade%2A> method.
 
 ## ClickOnce and roaming settings
+
  ClickOnce does not work with roaming settings, which allows your settings file to follow you across machines on a network. If you need roaming settings, you will need either to implement an application settings provider that stores settings over the network, or develop your own custom settings classes for storing settings on a remote computer. For more information in settings providers, see [Application settings architecture](/dotnet/framework/winforms/advanced/application-settings-architecture).
 
 ## See also
+
 - [ClickOnce security and deployment](../deployment/clickonce-security-and-deployment.md)
 - [Application settings overview](/dotnet/framework/winforms/advanced/application-settings-overview)
 - [ClickOnce cache overview](../deployment/clickonce-cache-overview.md)

docs/test/index.yml

@@ -78,7 +78,7 @@ landingContent:
         links:
           - text: Exploratory & manual testing (Azure Test Plans)
             url: /azure/devops/test/overview?view=azure-devops&preserve-view=true
-          - text: Load testing (Azure Test Plans)
+          - text: Load testing (Azure Load Testing)
             url: /azure/load-testing/
           - text: Continuous testing (Azure Pipelines)
             url: /azure/devops/pipelines/?view=azure-devops&preserve-view=true