You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| 1 |[Environment][env-cred]|Reads a collection of environment variables to determine if an application service principal (application user) is configured for the app. If so, `DefaultAzureCredential` uses these values to authenticate the app to Azure. This method is most often used in server environments but can also be used when developing locally. | Yes |
46
+
| 1 |[Environment][env-cred]|Reads a collection of [environment variables][env-vars] to determine if an application service principal (application user) is configured for the app. If so, `DefaultAzureCredential` uses these values to authenticate the app to Azure. This method is most often used in server environments but can also be used when developing locally. | Yes |
47
47
| 2 |[Workload Identity][wi-cred]|If the app is deployed to an Azure host with Workload Identity enabled, authenticate that account. | Yes |
48
48
| 3 |[Managed Identity][mi-cred]|If the app is deployed to an Azure host with Managed Identity enabled, authenticate the app to Azure using that Managed Identity. | Yes |
49
49
| 4 |[Visual Studio][vs-cred]|If the developer authenticated to Azure by logging into Visual Studio, authenticate the app to Azure using that same account. | Yes |
@@ -114,7 +114,7 @@ Here's why:
114
114
115
115
-**Debugging challenges**: When authentication fails, it can be challenging to debug and identify the offending credential. You must enable logging to see the progression from one credential to the next and the success/failure status of each. For more information, see [Debug a chained credential](#debug-a-chained-credential).
116
116
-**Performance overhead**: The process of sequentially trying multiple credentials can introduce performance overhead. For example, when running on a local development machine, managed identity is unavailable. Consequently, `ManagedIdentityCredential` always fails in the local development environment, unless explicitly disabled via its corresponding `Exclude`-prefixed property.
117
-
-**Unpredictable behavior**: `DefaultAzureCredential` checks for the presence of certain [environment variables](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/identity/Azure.Identity/README.md#environment-variables). It's possible that someone could add or modify these environment variables at the system level on the host machine. Those changes apply globally and therefore alter the behavior of `DefaultAzureCredential` at runtime in any app running on that machine.
117
+
-**Unpredictable behavior**: `DefaultAzureCredential` checks for the presence of certain [environment variables][env-vars]. It's possible that someone could add or modify these environment variables at the system level on the host machine. Those changes apply globally and therefore alter the behavior of `DefaultAzureCredential` at runtime in any app running on that machine.
118
118
119
119
## Debug a chained credential
120
120
@@ -130,3 +130,6 @@ In the preceding output, notice that:
130
130
131
131
-`EnvironmentCredential`, `WorkloadIdentityCredential`, and `ManagedIdentityCredential` each failed to acquire a Microsoft Entra access token, in that order.
132
132
- The `DefaultAzureCredential credential selected:`-prefixed entry indicates the credential that was selected—`VisualStudioCredential` in this case. Since `VisualStudioCredential` succeeded, no credentials beyond it were used.
|`Microsoft.NET.Sdk`| The .NET SDK |<https://github.com/dotnet/sdk>|
20
+
|`Microsoft.NET.Sdk.Web`| The .NET [Web SDK](/aspnet/core/razor-pages/web-sdk)|<https://github.com/dotnet/sdk>|
21
+
|`Microsoft.NET.Sdk.Razor`| The .NET [Razor SDK](/aspnet/core/razor-pages/sdk)|<https://github.com/dotnet/aspnetcore>|
22
22
|`Microsoft.NET.Sdk.BlazorWebAssembly`| The .NET [Blazor WebAssembly SDK](/aspnet/core/blazor#blazor-webassembly)|<https://github.com/dotnet/aspnetcore>|
23
-
|`Microsoft.NET.Sdk.Worker`| The .NET [Worker Service](../extensions/workers.md)SDK ||
24
-
|`Aspire.AppHost.Sdk`| The .NET Aspire SDK|<https://github.com/dotnet/aspire>|
25
-
|`MSTest.Sdk`| The [MSTest SDK](../testing/unit-testing-mstest-sdk.md)|<https://github.com/microsoft/testfx>|
23
+
|`Microsoft.NET.Sdk.Worker`| The .NET [Worker Service SDK](../extensions/workers.md)|<https://github.com/dotnet/aspnetcore>|
24
+
|`Aspire.AppHost.Sdk`| The .NET [Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk)|<https://github.com/dotnet/aspire>|
25
+
|`MSTest.Sdk`| The [MSTest SDK](../testing/unit-testing-mstest-sdk.md)|<https://github.com/microsoft/testfx>|
26
26
27
27
The .NET SDK is the base SDK for .NET. The other SDKs reference the .NET SDK, and projects that are associated with the other SDKs have all the .NET SDK properties available to them. The Web SDK, for example, depends on both the .NET SDK and the Razor SDK.
28
28
@@ -38,22 +38,22 @@ You can also author your own SDK that can be distributed via NuGet.
38
38
39
39
```xml
40
40
<ProjectSdk="Microsoft.NET.Sdk">
41
-
...
41
+
<!-- Omitted for brevity...-->
42
42
</Project>
43
43
```
44
44
45
-
Starting with .NET Aspire 9, the preceding example could instead use the .NET Aspire SDK.
45
+
The `Project/Sdk` attribute and `Sdk` element enable additive SDKs. Consider the following example, where the .NET Aspire SDK (`Aspire.AppHost.Sdk`) is added to the project atop the `Microsoft.NET.Sdk`:
For more information, see [.NET Aspire tooling and setup](/dotnet/aspire/fundamentals/setup-tooling).
56
+
In the preceding project file, both SDKs are used to resolve dependencies in an additive nature. For more information, see [.NET Aspire SDK](/dotnet/aspire/fundamentals/dotnet-aspire-sdk)
57
57
58
58
To specify an SDK that comes from NuGet, include the version at the end of the name, or specify the name and version in the *global.json* file.
Copy file name to clipboardExpand all lines: docs/core/testing/unit-testing-platform-integration-dotnet-test.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ By default, VSTest is used to run `Microsoft.Testing.Platform` tests. You can en
58
58
59
59
In this mode, you can supply extra parameters that are used to call the testing application in one of the following ways:
60
60
61
-
- Beginning with `Microsoft.Testing.Platform` version 1.4 (included with MSTest version 3.6), you can options after the double dash `--` on the command line:
61
+
- Beginning with `Microsoft.Testing.Platform` version 1.4 (included with MSTest version 3.6), you can add options after the double dash `--` on the command line:
0 commit comments