1. Microsoft User Data Folder Location
2. Microsoft User Data Folder Location

Fixed: where are my Office 365 AutoRecovery files?, Microsoft User Data, Microsoft Word. Default autosave folder location? Because my Mac crashes all the. How to connect Mac and Windows 10 PC and share files over a network File sharing between a Windows 10 PC and a Mac (running Mac OS X or macOS) is more complex than you'd imagine.

-->

1. Next, use the check disk (chkdsk) utility on your PC to make sure that your Windows drive doesn’t have any issues: Choose Start Run. In the Run window, type cmd and press Enter. In the command window, type chkdsk and press Enter.
2. Mar 19, 2020  I just upgraded from Office 2011 for the Mac to office 2016 (via an office 365 subscription). Can I delete the old 'microsoft user data' folder in my documents folder. My understanding is that office 2016 doesn't need it. Since I didn't use Outlook, the folder is small, but it is still clutter I'd like to get rid of if not needed.
3. Jul 05, 2017  Where Are My Outlook PST Data Files, and How Can I Move Them Somewhere Else? Walter Glenn @wjglenn Updated July 5, 2017, 11:08am EDT Most people know that Outlook stores email for each account in a personal table storage (PST) file, but figuring out where that file is located depends on what version of Outlook you’re using.

By Rick Anderson, Daniel Roth, and Scott Addie

View or download sample code (how to download)

This document explains techniques for storing and retrieving sensitive data during development of an ASP.NET Core app on a development machine. Never store passwords or other sensitive data in source code. Production secrets shouldn't be used for development or test. Secrets shouldn't be deployed with the app. Instead, secrets should be made available in the production environment through a controlled means like environment variables, Azure Key Vault, etc. You can store and protect Azure test and production secrets with the Azure Key Vault configuration provider.

Microsoft User Data Folder Location

Environment variables

Environment variables are used to avoid storage of app secrets in code or in local configuration files. Environment variables override configuration values for all previously specified configuration sources.

Configure the reading of environment variable values by calling AddEnvironmentVariables in the Startup constructor:

Consider an ASP.NET Core web app in which Individual User Accounts security is enabled. A default database connection string is included in the project's appsettings.json file with the key DefaultConnection. The default connection string is for LocalDB, which runs in user mode and doesn't require a password. During app deployment, the DefaultConnection key value can be overridden with an environment variable's value. The environment variable may store the complete connection string with sensitive credentials.

Warning

Environment variables are generally stored in plain, unencrypted text. If the machine or process is compromised, environment variables can be accessed by untrusted parties. Additional measures to prevent disclosure of user secrets may be required.

The : separator doesn't work with environment variable hierarchical keys on all platforms. __, the double underscore, is:

• Supported by all platforms. For example, the : separator is not supported by Bash, but __ is.
• Automatically replaced by a :

Secret Manager

The Secret Manager tool stores sensitive data during the development of an ASP.NET Core project. In this context, a piece of sensitive data is an app secret. App secrets are stored in a separate location from the project tree. The app secrets are associated with a specific project or shared across several projects. The app secrets aren't checked into source control.

Warning

The Secret Manager tool doesn't encrypt the stored secrets and shouldn't be treated as a trusted store. It's for development purposes only. The keys and values are stored in a JSON configuration file in the user profile directory.

How the Secret Manager tool works

The Secret Manager tool abstracts away the implementation details, such as where and how the values are stored. You can use the tool without knowing these implementation details. The values are stored in a JSON configuration file in a system-protected user profile folder on the local machine:

File system path:

%APPDATA%MicrosoftUserSecrets<user_secrets_id>secrets.json

File system path:

~/.microsoft/usersecrets/<user_secrets_id>/secrets.json

In the preceding file paths, replace <user_secrets_id> with the UserSecretsId value specified in the .csproj file.

Don't write code that depends on the location or format of data saved with the Secret Manager tool. These implementation details may change. For example, the secret values aren't encrypted, but could be in the future.

Install the Secret Manager tool

The Secret Manager tool is bundled with the .NET Core CLI in .NET Core SDK 2.1.300 or later. For .NET Core SDK versions before 2.1.300, tool installation is necessary.

Tip

Run dotnet --version from a command shell to see the installed .NET Core SDK version number.

A warning is displayed if the .NET Core SDK being used includes the tool:

Install the Microsoft.Extensions.SecretManager.Tools NuGet package in your ASP.NET Core project. For example:

Execute the following command in a command shell to validate the tool installation:

The Secret Manager tool displays sample usage, options, and command help:

Note

You must be in the same directory as the .csproj file to run tools defined in the .csproj file's DotNetCliToolReference elements.

Enable secret storage

The Secret Manager tool operates on project-specific configuration settings stored in your user profile.

The Secret Manager tool includes an init command in .NET Core SDK 3.0.100 or later. To use user secrets, run the following command in the project directory:

The preceding command adds a UserSecretsId element within a PropertyGroup of the .csproj file. By default, the inner text of UserSecretsId is a GUID. The inner text is arbitrary, but is unique to the project.

To use user secrets, define a UserSecretsId element within a PropertyGroup of the .csproj file. The inner text of UserSecretsId is arbitrary, but is unique to the project. Developers typically generate a GUID for the UserSecretsId.

Tip

In Visual Studio, right-click the project in Solution Explorer, and select Manage User Secrets from the context menu. This gesture adds a UserSecretsId element, populated with a GUID, to the .csproj file.

Set a secret

Define an app secret consisting of a key and its value. The secret is associated with the project's UserSecretsId value. For example, run the following command from the directory in which the .csproj file exists:

In the preceding example, the colon denotes that Movies is an object literal with a ServiceApiKey property.

The Secret Manager tool can be used from other directories too. Use the --project option to supply the file system path at which the .csproj file exists. For example:

JSON structure flattening in Visual Studio

Visual Studio's Manage User Secrets gesture opens a secrets.json file in the text editor. Replace the contents of secrets.json with the key-value pairs to be stored. For example:

The JSON structure is flattened after modifications via dotnet user-secrets remove or dotnet user-secrets set. For example, running dotnet user-secrets remove 'Movies:ConnectionString' collapses the Movies object literal. The modified file resembles the following:

Set multiple secrets

A batch of secrets can be set by piping JSON to the set command. In the following example, the input.json file's contents are piped to the set command.

Open a command shell, and execute the following command:

Open a command shell, and execute the following command:

Access a secret

The ASP.NET Core Configuration API provides access to Secret Manager secrets.

If your project targets .NET Framework, install the Microsoft.Extensions.Configuration.UserSecrets NuGet package.

In ASP.NET Core 2.0 or later, the user secrets configuration source is automatically added in development mode when the project calls CreateDefaultBuilder to initialize a new instance of the host with preconfigured defaults. CreateDefaultBuilder calls AddUserSecrets when the EnvironmentName is Development:

When CreateDefaultBuilder isn't called, add the user secrets configuration source explicitly by calling AddUserSecrets in the Startup constructor. Call AddUserSecrets only when the app runs in the Development environment, as shown in the following example:

Install the Microsoft.Extensions.Configuration.UserSecrets NuGet package.

Add the user secrets configuration source with a call to AddUserSecrets in the Startup constructor:

Microsoft outlook 2011 mac stopped working. User secrets can be retrieved via the Configuration API:

Map secrets to a POCO

Mapping an entire object literal to a POCO (a simple .NET class with properties) is useful for aggregating related properties.

Assume the app's secrets.json file contains the following two secrets:

To place a text box in your document, choose Insert→Text Box. .Text boxes: Text boxes let you place a chunk of text somewhere on a page without setting margins, indents, columns, or tables. Microsoft word 2008 mac create links. Your cursor turns into a special text box placing cursor.

To map the preceding secrets to a POCO, use the Configuration API's object graph binding feature. The following code binds to a custom MovieSettings POCO and accesses the ServiceApiKey property value:

The Movies:ConnectionString and Movies:ServiceApiKey secrets are mapped to the respective properties in MovieSettings:

String replacement with secrets

Storing passwords in plain text is insecure. For example, a database connection string stored in appsettings.json may include a password for the specified user:

A more secure approach is to store the password as a secret. For example:

Remove the Password key-value pair from the connection string in appsettings.json. For example:

The secret's value can be set on a SqlConnectionStringBuilder object's Password property to complete the connection string:

List the secrets

Assume the app's secrets.json file contains the following two secrets:

Run the following command from the directory in which the .csproj file exists:

The following output appears:

In the preceding example, a colon in the key names denotes the object hierarchy within secrets.json.

Remove a single secret

Assume the app's secrets.json file contains the following two secrets:

Run the following command from the directory in which the .csproj file exists:

The app's secrets.json file was modified to remove the key-value pair associated with the MoviesConnectionString key:

Running dotnet user-secrets list displays the following message:

Remove all secrets

Assume the app's secrets.json file contains the following two secrets:

Run the following command from the directory in which the .csproj file exists:

All user secrets for the app have been deleted from the secrets.json file:

Running dotnet user-secrets list displays the following message:

Additional resources

Microsoft User Data Folder Location

• See this issue for information on accessing Secret Manager from IIS.