Merge branch 'azure-sdk:main' into main

Author: Unity-Billal-mesloub

.config/1espt/PipelineAutobaseliningConfig.yml

@@ -1,5 +1,5 @@
-## DO NOT MODIFY THIS FILE MANUALLY. This is part of auto-baselining from 1ES Pipeline Templates. Go to [https://aka.ms/1espt-autobaselining] for more details.
-
+## DO NOT MODIFY THIS FILE MANUALLY. This is part of auto-baselining from 1ES Pipeline Templates. Go to [https://aka.ms/1espt-autobaselining] for more details.
+
 pipelines:
   '*':
     mainPipelineId: 1180

.gitattributes

@@ -1,4 +1,4 @@
-* text=auto
+* text=auto eol=lf
 
 *.bmp binary
 *.dll binary
@@ -12,10 +12,12 @@
 *.ismv binary
 *.isma binary
 
-*.cs text diff=csharp
-*.csproj text=auto
-*.sln text=auto eol=crlf
-*.sh text=auto eol=lf
+*.cs     text eol=lf diff=csharp
+*.csproj text eol=lf
+*.sln    text eol=lf
+*.sh     text eol=lf
+*.json   text eol=lf
+*.bicep  text eol=lf
 
 # Automatically collapse Track 2 test recordings in github PRs
 **/SessionRecords/**/*.json linguist-generated=true

.github/CODEOWNERS

@@ -1,3 +1,26 @@
+# Project Overview
+
+This repo contains Azure SDKs for various Azure services and tools that generate them.
+
+## Prerequisites
+- To use MCP tool calls, PowerShell must be installed. Provide [PowerShell installation instructions](https://learn.microsoft.com/powershell/scripting/install/installing-powershell) if not installed, and recommend restarting the IDE to use the MCP server.
+
+## Folder Structure
+
+- `/eng/packages/http-client-csharp`: Contains the source code of the generator for Azure Data Plane SDKs (aka Azure Generator).
+- `/eng/packages/http-client-csharp-mgmt`: Contains the source code of the generator for Azure Management Plane SDKs (aka Azure Management Generator).
+- `/sdk`: Contains the individual SDKs for Azure services.
+
+### Azure Generator
+
+- Always run `npm install` in the `/eng/packages/http-client-csharp` directory before running the generator.
+- Always run `/eng/packages/http-client-csharp/eng/scripts/Generate.ps1` to regenerate the test projects to validate the result of generator code changes.
+
+### Azure Management Generator
+
+- Always run `npm install` in the `/eng/packages/http-client-csharp-mgmt` directory before running the generator.
+- Always run `/eng/packages/http-client-csharp-mgmt/eng/scripts/Generate.ps1` to regenerate the test projects to validate the result of generator code changes.
+
 ## SDK release
 
 There are two tools to help with SDK releases:

.github/copilot-instructions.md

@@ -36,3 +36,9 @@ jobs:
       # Example: Display .NET SDK version
       - name: Show .NET SDK version
         run: dotnet --version
+
+      - name: Install azsdk mcp server
+        shell: pwsh
+        run: |
+          ./eng/common/mcp/azure-sdk-mcp.ps1 -InstallDirectory $HOME/bin
+

.github/workflows/copilot-setup-steps.yml

@@ -1249,6 +1249,12 @@
         "unprovisioning"
       ]
     },
+    {
+      "filename": "**/sdk/recoveryservices/**/*.cs",
+      "words": [
+        "bcdr",
+      ]
+    },
     {
       "filename": "**/sdk/recoveryservices-backup/**/*.cs",
       "words": [

.vscode/cspell.json

@@ -0,0 +1,11 @@
+// Copyright (c) Microsoft Corporation. All rights reserved.
+// Licensed under the MIT License.
+
+namespace Azure.Test.Perf
+{
+    public class OperationResult
+    {
+        public double Time { get; set; }
+        public long Size { get; set; }
+    }
+}

common/Perf/Azure.Test.Perf/OperationResult.cs

@@ -54,6 +54,9 @@ public class PerfOptions
         [Option('x', "test-proxies", Separator = ';', HelpText = "URIs of TestProxy Servers (separated by ';')")]
         public IEnumerable<Uri> TestProxies { get; set; }
 
+        [Option("results-file", HelpText = "File path location to store the results for the test run.")]
+        public string ResultsFile { get; set; }
+
         [Option('w', "warmup", Default = 5, HelpText = "Duration of warmup in seconds")]
         public int Warmup { get; set; }
     }

common/Perf/Azure.Test.Perf/PerfOptions.cs

@@ -7,6 +7,7 @@
 using System;
 using System.Collections.Generic;
 using System.Diagnostics;
+using System.IO;
 using System.Linq;
 using System.Reflection;
 using System.Runtime;
@@ -457,6 +458,11 @@ private static async Task RunTestsAsync(IPerfTest[] tests, PerfOptions options,
                 {
                     PrintLatencies("Corrected Latency Distribution", _correctedLatencies);
                 }
+
+                if (!string.IsNullOrEmpty(options.ResultsFile))
+                {
+                    WriteResults(options.ResultsFile, (options as SizeOptions)?.Size ?? -1);
+                }
             }
 
             if (jobStatistics)
@@ -498,6 +504,20 @@ private static void PrintLatencies(string header, IList<IList<TimeSpan>> latenci
             Console.WriteLine();
         }
 
+        private static void WriteResults(string path, long operationSize)
+        {
+            var latencies = _latencies.SelectMany(x => x).Select(l => new OperationResult
+            {
+                Time = l.TotalMilliseconds,
+                Size = operationSize,
+            }).ToArray();
+            string json = JsonSerializer.Serialize(latencies, options: new JsonSerializerOptions()
+            {
+                WriteIndented = true,
+            });
+            File.WriteAllText(path, json);
+        }
+
         private static Thread WritePendingOperations(int rate, CancellationToken token)
         {
             var thread = new Thread(() =>

common/Perf/Azure.Test.Perf/PerfProgram.cs

@@ -6,17 +6,19 @@ Azure SDK Code Generation takes a [TypeSpec](https://microsoft.github.io/typespe
 
 ## Prerequisites
 
+The initial library generation should happen as part of the `azure-rest-api-specs` repo PR. Details about this process can be found [here](https://eng.ms/docs/products/azure-developer-experience/develop/sdk-generation-pipelines). To proceed with manual generation, follow the rest of the steps in this doc.
+
 For first time to set up of a new SDK package, please verify you have met the prerequisites, including runtime environment, TypeSpec project, and SDK project folder. You can refer to [SDK Generation Prerequisites](https://github.com/Azure/azure-sdk-for-net/blob/main/doc/DataPlaneCodeGeneration/AzureSDKGeneration_Prerequistites.md) to set up.
 
 ## Generate SDK
 
 We will generate an SDK under the SDK project folder of `azure-sdk-for-net`.
 
-### Configuration (optional)
+### Configuration
 
 You can update `tsp-location.yaml` under sdk project folder to set the typespec project.
 
-You can refer to the [tsp-location.yaml](https://github.com/Azure/azure-sdk-tools/blob/main/doc/common/TypeSpec-Project-Scripts.md#tsp-locationyaml) which describes the supported properties in the file.
+You can refer to the [tsp-location.yaml](https://github.com/Azure/azure-sdk-tools/blob/main/doc/common/TypeSpec-Project-Scripts.md#tsp-locationyaml) which describes the supported properties in the file. For new data plane services, you must set the `emitterPackageJsonPath` property in tsp-location.yaml to `eng/azure-typespec-http-client-csharp-emitter-package.json`. An example can be found [here](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/keyvault/Azure.Security.KeyVault.Administration/tsp-location.yaml#L4). You should add the `IncludeAutorestDependency` property and set it to `false` in the corresponding csproj that is generated. An example can be found [here](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/keyvault/Azure.Security.KeyVault.Administration/src/Azure.Security.KeyVault.Administration.csproj#L14).
 
 ### Generate Code
 
@@ -27,6 +29,18 @@ Run `dotnet build /t:GenerateCode`, and the code will be generated under `sdk\<s
 dotnet build /t:GenerateCode
 ```
 
+#### Run with tracing enabled
+```dotnetcli
+dotnet build /t:GenerateCode /p:Trace=true -v d
+```
+
+#### Run with additional emitter options
+Any of the [emitter options](https://github.com/Azure/azure-sdk-for-net/blob/main/eng/packages/http-client-csharp/README.md#emitter-options) can be passed through to the build target
+as shown below:
+```dotnetcli
+dotnet build /t:GenerateCode /p:TypespecAdditionalOptions="debug=true;new-project=true"
+```
+
 Now that you have generated your SDK, you can release it by following the following steps:
 
 1. Create a [release plan](https://aka.ms/azsdkdocs/release-plans). It will provide you with a workflow of tasks that you