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
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,11 +31,7 @@ Note: Only applies to `Microsoft.Azure.Management.[RP]` or `Azure.ResourceManage
31
31
- Do not modify any code in generated folders.
32
32
- Do not selectively include/remove generated files in the PR.
33
33
- Do use `generate.ps1/cmd` to generate this PR instead of calling `autorest` directly.
34
-
Please pay attention to the @microsoft.csharp version output after running `generate.ps1`. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.
35
-
36
-
**Note: We have recently updated the PSH module called by `generate.ps1` to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command**:
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+14-15Lines changed: 14 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,12 +197,12 @@ When run, the code regions in the format below (where `<snippetName>` is the nam
197
197
//some sample code
198
198
stringsnippet="some snippet code";
199
199
200
-
//The snippet updater defines the SNIPPET directive while parsing. You can use #if SNIPPET to filter lines in or out of the snippet.
201
-
#ifSNIPPET
202
-
snippet="value that would never pass a test but looks good in a sample!";
203
-
#else
204
-
stringignored="this code will not appear in the snippet markdown";
205
-
#endif
200
+
//Lines prefixed with the below comment format will be ignored by the snippet updater.
201
+
/*@@*/stringignored="this code will not appear in the snippet markdown";
202
+
203
+
// Lines prefixed with the below comment format will appear in the snippet markdown, but will remain comments in the C#` code.
204
+
// Note: these comments should only be used for non-critical code as it will not be compiled or refactored as the code changes.
205
+
//@@ snippet = "value that would never pass a test but looks good in a sample!";
206
206
207
207
#endregion
208
208
```
@@ -324,16 +324,15 @@ As you can see in the example below, we want to use the `Azure.Data.Tables` vers
324
324
325
325
## Preparing a new library release
326
326
327
-
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.
327
+
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 as well as the release date. This script will correctly update the package version in the repo as well as update DevOps release work items for that release.
If you are releasing out-of-band please use the `-ReleaseDate` parameter to specify the release data. `ReleaseDate` should be in `yyyy-MM-dd` format.
332
330
333
-
-`<PackageName>` - Should match the full exact package name for the given ecosystem (i.e. "Azure.Core", "azure-core", "@azure/core", etc).
334
-
-`<SerivceDirectory>` - Optional: Should be the exact directory name where the package resides in the repo. This is usually the same as the service name in most cases (i.e. "sdk<service_directory>" e.g. "core"). The parameter is optional and if provided will help speed-up the number of projects we have to parse to find the matching package project.
335
-
-`<ReleaseDate>` - Optional: provide a specific date for when you plan to release the package. If one isn't given then one will be calculated based on the normal monthly shipping schedule.
336
-
-`<ReleaseTrackingOnly>` - Optional: Switch that if passed will only update the release tracking data in DevOps and not update any versioning info or do validation in the local repo.
@@ -524,4 +523,4 @@ For more information on how we version see [Versioning](https://github.com/Azure
524
523
525
524
## Breaking Changes
526
525
527
-
For information about breaking changes see [Breaking Change Rules](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-change-rules.md)
526
+
For information about breaking changes see [Breaking Change Rules](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/breaking-change-rules.md)
<IsLegacyMgmtProjectCondition="'$(IsLegacyMgmtProject)' == '' and $(MSBuildProjectName.Contains('.Management.'))">true</IsLegacyMgmtProject>
8
-
<ProjectStartsWithStandardNameCondition="$(MSBuildProjectName.StartsWith('Azure.')) or $(MSBuildProjectName.StartsWith('Microsoft.'))">true</ProjectStartsWithStandardName>
9
-
<ImportRepoCommonSettingsCondition="'$(ImportRepoCommonSettings)' == '' and '$(ProjectStartsWithStandardName)' == 'true' and '$(IsLegacyMgmtProject)' != 'true'">true</ImportRepoCommonSettings>
7
+
<IsClientLibraryCondition="'$(IsClientLibrary)' == '' and $(MSBuildProjectName.StartsWith('Azure.'))">true</IsClientLibrary>
8
+
<IsDataPlaneProjectCondition="'$(IsDataPlaneProject)' == '' and '$(IsClientLibrary)' == 'true'">true</IsDataPlaneProject>
Copy file name to clipboardExpand all lines: README.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
@@ -35,7 +35,7 @@ Last stable versions of packages that are production-ready. These libraries prov
35
35
36
36
A new set of management libraries that follow the [Azure SDK Design Guidelines for .NET](https://azure.github.io/azure-sdk/dotnet_introduction.html) and based on [Azure.Core libraries](https://github.com/Azure/azure-sdk-for-net/tree/master/sdk/core/Azure.Core) are now in Public Preview. These new libraries provide a number of core capabilities that are shared amongst all Azure SDKs, including the intuitive Azure Identity library, an HTTP Pipeline with custom policies, error-handling, distributed tracing, and much more. You can find the list of new packages [on this page](https://azure.github.io/azure-sdk/releases/latest/dotnet.html).
37
37
38
-
To get started with these new libraries, please see the [quickstart guide here](https://github.com/Azure/azure-sdk-for-net/blob/master/doc/mgmt_preview_quickstart.md). These new libraries can be identified by namespaces that start with `Azure.ResourceManager`, e.g. `Azure.ResourceManager.Network`
38
+
To get started with these new libraries, please see the [quickstart guide here](https://github.com/Azure/azure-sdk-for-net/blob/master/doc/mgmt_preview_quickstart.md). These new libraries can be identifed by namespaces that start with `Azure.ResourceManager`, e.g. `Azure.ResourceManager.Network`
39
39
40
40
> NOTE: If you need to ensure your code is ready for production use one of the stable, non-preview libraries.
0 commit comments