|
49 | 49 | <altmember cref="T:System.Configuration.ApplicationSettingsBase" />
|
50 | 50 | <altmember cref="T:System.Configuration.ClientSettingsSection" />
|
51 | 51 | <altmember cref="T:System.Configuration.IConfigurationSectionHandler" />
|
52 |
| - <related type="Article" href="https://msdn.microsoft.com/library/c8eb2ad0-fac6-4ea2-9140-675a4a44d562">Application Settings Architecture</related> |
| 52 | + <related type="Article" href="~/docs/framework/winforms/advanced/application-settings-architecture.md">Application Settings Architecture</related> |
53 | 53 | </Docs>
|
54 | 54 | <Members>
|
55 | 55 | <Member MemberName=".ctor">
|
|
228 | 228 | The <xref:System.Configuration.LocalFileSettingsProvider.GetPropertyValues%2A> method also manages the special application settings type <xref:System.Configuration.SpecialSetting.ConnectionString>. Connection strings are stored in a special section of the configuration file delimited by the element `<connectionstrings>`.
|
229 | 229 |
|
230 | 230 | > [!CAUTION]
|
231 |
| -> <xref:System.Configuration.LocalFileSettingsProvider> does not use encryption to persist any settings. Therefore, do not store plain text passwords or other sensitive information using this provider without taking additional precautions, such as separately encrypting the information within the configuration file. For more information, see [Encrypting Configuration Information Using Protected Configuration](https://msdn.microsoft.com/library/51cdfe5b-9d82-458c-94ff-c551c4f38ed1). |
| 231 | +> <xref:System.Configuration.LocalFileSettingsProvider> does not use encryption to persist any settings. Therefore, do not store plain text passwords or other sensitive information using this provider without taking additional precautions, such as separately encrypting the information within the configuration file. For more information, see [Encrypting Configuration Information Using Protected Configuration](https://docs.microsoft.com/previous-versions/aspnet/53tyfkaw(v=vs.100)). |
232 | 232 |
|
233 | 233 | ]]></format>
|
234 | 234 | </remarks>
|
|
387 | 387 | If a user-scoped settings property is set back to its default value explicitly, then the local file settings provider will remove the entry for the associated setting from the user configuration file. The next read access for this property will simply use the default value.
|
388 | 388 |
|
389 | 389 | > [!CAUTION]
|
390 |
| -> <xref:System.Configuration.LocalFileSettingsProvider> does not use encryption to persist any settings. Therefore, do not store plain text passwords or other sensitive information using this provider without taking additional precautions, such as separately encrypting the information within the configuration file. For more information, see [Encrypting Configuration Information Using Protected Configuration](https://msdn.microsoft.com/library/51cdfe5b-9d82-458c-94ff-c551c4f38ed1). |
| 390 | +> <xref:System.Configuration.LocalFileSettingsProvider> does not use encryption to persist any settings. Therefore, do not store plain text passwords or other sensitive information using this provider without taking additional precautions, such as separately encrypting the information within the configuration file. For more information, see [Encrypting Configuration Information Using Protected Configuration](https://docs.microsoft.com/previous-versions/aspnet/53tyfkaw(v=vs.100)). |
391 | 391 |
|
392 | 392 | ]]></format>
|
393 | 393 | </remarks>
|
|
451 | 451 |
|
452 | 452 | This way this method is called depends on the type of application that is being upgraded:
|
453 | 453 |
|
454 |
| -- Each version of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is stored in its own isolated installation directory. After a new version of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is installed, and when the new version is first run, internal logic will automatically call <xref:System.Configuration.LocalFileSettingsProvider.Upgrade%2A> to migrate all common application settings to the new version. For more information, see [ClickOnce and Application Settings](https://msdn.microsoft.com/library/891caba6-faef-4a3c-8f71-60e6fadb60eb). |
| 454 | +- Each version of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is stored in its own isolated installation directory. After a new version of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is installed, and when the new version is first run, internal logic will automatically call <xref:System.Configuration.LocalFileSettingsProvider.Upgrade%2A> to migrate all common application settings to the new version. For more information, see [ClickOnce and Application Settings](/visualstudio/deployment/clickonce-and-application-settings). |
455 | 455 |
|
456 | 456 | - Standard Windows Forms and console applications must manually call <xref:System.Configuration.LocalFileSettingsProvider.Upgrade%2A>, because there is not a general, automatic way to determine when such an application is first run. The two common ways to do this are either from the installation program or using from the application itself, using a persisted property, often named something like `IsFirstRun`.
|
457 | 457 |
|
|
0 commit comments