daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

get rid of curly apostrophes

sharedenvvars
Tom Dykstra 2024-12-25 09:17:13 -08:00
parent 7ad76dd4fa
commit 9169d917a1
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
aspnetcore/test/http-files.md
View File

@ -192,7 +192,7 @@ In the preceding example, the `$shared` environment defines the `HostAddress` va
## User-specific environment files
A user-specific value is any value that an individual developer wants to test with but doesn’t want to share with the team. Since the `http-client.env.json` file is checked in to source control by default, it wouldn’t be appropriate to add user-specific values to this file. Instead, put them in a file named `http-client.env.json.user` located in the same folder as the `http-client.env.json` file. Files that end with `.user` should be excluded from source control by default when using Visual Studio source control features.
A user-specific value is any value that an individual developer wants to test with but doesn't want to share with the team. Since the `http-client.env.json` file is checked in to source control by default, it wouldn't be appropriate to add user-specific values to this file. Instead, put them in a file named `http-client.env.json.user` located in the same folder as the `http-client.env.json` file. Files that end with `.user` should be excluded from source control by default when using Visual Studio source control features.
When the `http-client.env.json` file is loaded, Visual Studio looks for a sibling `http-client.env.json.user` file. If a variable is defined in an environment in both the `http-client.env.json` file and the `http-client.env.json.user` file, the value in the `http-client.env.json.user` file wins.
@ -354,7 +354,7 @@ GET {{HostAddress}}{{Path}}
X-UserName: {{$processEnv USERNAME}}
```
If you try to use `$processEnv` to access an environment variable that doesn’t exist, the `.http` file editor displays an error message.
If you try to use `$processEnv` to access an environment variable that doesn't exist, the `.http` file editor displays an error message.
## `.env` files