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
Drop netcoreapp3.1, add net7.0 support (Azure#32814)
* Drop netcoreapp3.1, add net7.0 support
ResolvesAzure#32596. With netcoreapp3.1 falling out of support soon, we're upgrading to net7.0, net6.0, and, on Windows, net461.
* Resolve PR comments and fix build break
* Tweak platform monikers
* Upgrade to .NET 7.0.101 SDK
Required for microsoft/vstest#4014 fix
* Drop unnecessary runtimes from .vsconfig
* Skip Monitor tests failing under net7.0
Relates to Azure#33403
* Resolve track 1 management plane issues on net7.0
* Resolve Key Vault issues after upgrade to net7.0
* Use different platform guard for management plane
* Resolve PR feedback
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-14
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,8 @@
8
8
9
9
- Install Visual Studio 2022 (Community or higher) and make sure you have the latest updates (https://www.visualstudio.com/).
10
10
- Need at least .NET Framework 4.6.1 and 4.7 development tools
11
-
- Install the **.NET Core cross-platform development** workloads in VisualStudio
12
-
- Install **.NET Core 6.0.100 SDK** for your specific platform. (or a higher version within the 6.0.*** band) (https://dotnet.microsoft.com/download/dotnet-core/6.0)
11
+
- Install the **.NET cross-platform development** workloads in VisualStudio
12
+
- Install **.NET 7.0.100 SDK** for your specific platform. (or a higher version within the 7.0.*** band) (https://dotnet.microsoft.com/download/dotnet-core/7.0)
13
13
- Install the latest version of git (https://git-scm.com/downloads)
14
14
- Install [PowerShell](https://docs.microsoft.com/powershell/scripting/install/installing-powershell), version 6 or higher, if you plan to make public API changes or are working with generated code snippets.
15
15
- Install [NodeJS](https://nodejs.org/) (16.x.x) if you plan to use [C# code generation](https://github.com/Azure/autorest.csharp).
@@ -182,7 +182,7 @@ In some cases, you might want to test against the latest versions of the client
182
182
183
183
If you make public API changes or additions, the `eng\scripts\Export-API.ps1` script has to be run to update public API listings. This generates a file in the library's directory similar to the example found in `sdk\template\Azure.Template\api\Azure.Template.netstandard2.0.cs`.
184
184
185
-
Running the script for a project in `sdk\tables` would look like this:
185
+
Running the script for a project in `sdk\tables` would look like this:
If the specific client library has sample snippets in markdown format, they were most likely created with help of the `eng\scripts\Update-Snippets.ps1` script.
192
192
Any changes made to the snippet markdown should be done via updating the corresponding C# snippet code and subsequently running the script.
193
193
194
-
Running the script for a project, for example in `sdk\keyvault`, would look like this:
194
+
Running the script for a project, for example in `sdk\keyvault`, would look like this:
195
195
```
196
196
eng\scripts\Update-Snippets.ps1 keyvault
197
197
```
@@ -211,13 +211,13 @@ string ignored = "this code will not appear in the snippet markdown";
211
211
212
212
#endregion
213
213
```
214
-
will be mapped to any markdown file with a corresponding code region in the format below where the snippet names match:
214
+
will be mapped to any markdown file with a corresponding code region in the format below where the snippet names match:
215
215
216
216
**\`\`\`C# Snippet:\<snippetName>**
217
217
218
218
**\`\`\`**
219
219
220
-
See the following example of a [snippet C# file](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/search/Azure.Search.Documents/tests/Samples/Sample01_HelloWorld.cs) and a [snippet markdown file](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/search/Azure.Search.Documents/samples/Sample01a_HelloWorld.md).
220
+
See the following example of a [snippet C# file](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/search/Azure.Search.Documents/tests/Samples/Sample01_HelloWorld.cs) and a [snippet markdown file](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/search/Azure.Search.Documents/samples/Sample01a_HelloWorld.md).
221
221
Note that snippet names need to be globally unique under a given service directory.
222
222
223
223
Snippets also can be integrated into XML doc comments. For example:
@@ -238,7 +238,7 @@ For general information about samples, see the [Samples Guidelines](https://azur
238
238
239
239
## Updating Source on Build
240
240
You can run `eng\scripts\Export-API.ps1` and `eng\scripts\Update-Snippets.ps1` simultaneously as part of the build by setting as true either:
241
-
1. The property `UpdateSourceOnBuild`
241
+
1. The property `UpdateSourceOnBuild`
242
242
2. The Environment variable `AZURE_DEV_UPDATESOURCESONBUILD=true`
243
243
244
244
e.g.
@@ -329,7 +329,7 @@ As you can see in the example below, we want to use the `Azure.Data.Tables` vers
329
329
330
330
## Preparing a new library release
331
331
332
-
To prepare a package for release you should make use of `.\eng\common\scripts\Prepare-Release.ps1` script passing it appropriate arguments for the package intended for release. This script will correctly update the package version and changelog in the repo as well as update the DevOps release work items for that release.
332
+
To prepare a package for release you should make use of `.\eng\common\scripts\Prepare-Release.ps1` script passing it appropriate arguments for the package intended for release. This script will correctly update the package version and changelog in the repo as well as update the DevOps release work items for that release.
Copy file name to clipboardExpand all lines: eng/Directory.Build.Common.props
+1-1
Original file line number
Diff line number
Diff line change
@@ -123,7 +123,7 @@
123
123
<PropertyGroupCondition="'$(IsTestProject)' == 'true' or '$(IsTestSupportProject)' == 'true' or '$(IsSamplesProject)' == 'true' or '$(IsPerfProject)' == 'true' or '$(IsStressProject)' == 'true'">
124
124
<IsPackable>false</IsPackable>
125
125
<!-- List newest targets first so that recordings are made with latest, running tests from editor runs latest, etc. -->
# Installation steps need to be uncommented when switching to a newer SDK that's not available on DevOps agents
14
14
- task: UseDotNet@2
15
-
displayName: 'Use .NET Core SDK'
15
+
displayName: 'Use .NET SDK'
16
16
retryCountOnTaskFailure: 3
17
17
inputs:
18
18
useGlobalJson: true
19
19
performMultiLevelLookup: true
20
+
- task: UseDotNet@2
21
+
condition: and(succeeded(), ne(variables['Agent.OS'], 'Windows_NT')) # Windows supports MultiLevelLookup and doesn't need explicit framework installation
22
+
displayName: 'Use .NET 6.0 SDK'
23
+
retryCountOnTaskFailure: 3
24
+
inputs:
25
+
# AspNetCore runtime pack can't be installed outside of SDK and we need it for integration tests
26
+
packageType: sdk
27
+
performMultiLevelLookup: true
28
+
version: "6.0.x"
20
29
- task: UseDotNet@2
21
30
condition: and(succeeded(), ne(variables['Agent.OS'], 'Windows_NT')) # Windows supports MultiLevelLookup and doesn't need explicit framework installation
Copy file name to clipboardExpand all lines: sdk/appconfiguration/CONTRIBUTING.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -22,9 +22,9 @@ Before working on a contribution, it would be beneficial to familiarize yourself
22
22
23
23
These libraries follow the [Azure SDK Design Guidelines for .NET][sdk_design_guidelines_dotnet] and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. You can learn about these shared features in the [Azure.Core README][sdk_dotnet_code_readme].
24
24
25
-
## Public API changes
25
+
## Public API changes
26
26
27
-
To update [`Azure.Data.AppConfiguration.netstandard2.0.cs`][azconfig_api] after making changes to the public API, execute [`./eng/scripts/Export-API.ps1`][azconfig_export_api].
27
+
To update [`Azure.Data.AppConfiguration.netstandard2.0.cs`][azconfig_api] after making changes to the public API, execute [`./eng/scripts/Export-API.ps1`][azconfig_export_api].
28
28
29
29
## Testing
30
30
@@ -48,7 +48,7 @@ Properly supporting recorded tests does require a few extra considerations. All
48
48
49
49
The easiest way to run the tests is via Visual Studio's unit test runner.
50
50
51
-
You can also run tests via the command line using `dotnet test`, but that will run tests for all supported platforms simultaneously and intermingle their output. You can run the tests for just one platform with `dotnet test -f netcoreapp3.1` or `dotnet test -f net461`.
51
+
You can also run tests via the command line using `dotnet test`, but that will run tests for all supported platforms simultaneously and intermingle their output. You can run the tests for just one platform with `dotnet test -f net6.0` or `dotnet test -f net461`.
52
52
53
53
The recorded tests are run automatically on every pull request. Live tests are run nightly. Contributors with write access can ask Azure DevOps to run the live tests against a pull request by commenting `/azp run net - appconfiguration - tests` in the PR.
0 commit comments