Task 43695: Use dotnet CLI exclusively

- Removed use of MSBuild in pipelines and documentation.
- Legacy build.proj still uses it, and will be replaced shortly by build2.proj which uses the dotnet CLI exclusively.

Author: paulmedynski

.github/copilot-instructions.md

@@ -21,7 +21,7 @@ The project includes:
   - **Manual Tests**: Located in `tests/ManualTests/` directory, which includes tests that require a SQL Server instance to run.
 - **Documentation**: Found in the `doc/` directory, including API documentation, usage examples.
 - **Policies**: Contribution guidelines, coding standards, and review policies in the `policy/` directory.
-- **Building**: The project uses MSBuild for building and testing, with configurations and targets defined in the `build.proj` file, whereas instructions are provided in the `BUILDGUIDE.md` file.
+- **Building**: The project uses `dotnet build` for building and testing, with configurations and targets defined in the `build.proj` file, whereas instructions are provided in the `BUILDGUIDE.md` file.
 - **CI/CD**: ADO Pipelines for CI/CD and Pull request validation are defined in the `eng/` directory, ensuring code quality and automated testing.
 
 ## 📦 Products

.github/instructions/ado-pipelines.instructions.md

@@ -48,7 +48,7 @@ Key parameters:
 - `runAlwaysEncryptedTests` — include AE test set; default `true`
 - `enableStressTests` — enable stress test stage; default `false`
 - `debug` — enable debug output; default `false`
-- `dotnetVerbosity` — MSBuild verbosity; default `normal`
+- `dotnetVerbosity` — build verbosity; default `normal`
 
 ## Build Stage Order
 

.github/instructions/architecture.instructions.md

@@ -48,7 +48,7 @@ The `netcore/` and `netfx/` directories are legacy artifacts from the old dual-p
 - `netcore/ref/` and `netfx/ref/` — **STILL ACTIVE**. Reference assemblies remain in these directories and define the public API surface for each target framework.
 
 ### OS Targeting with `TargetOs`
-The unified project uses a `TargetOs` MSBuild property to handle OS-specific compilation:
+The unified project uses a `TargetOs` build property to handle OS-specific compilation:
 
 ```xml
 <!-- Automatic OS detection -->

.github/instructions/testing.instructions.md

@@ -113,7 +113,7 @@ The default test filter is defined in `build.proj`:
 ```xml
 <FilterStatement Condition="'$(FilterStatement)' == ''">category!=failing&amp;category!=flaky</FilterStatement>
 ```
-This can be overridden via MSBuild property: `msbuild -p:FilterStatement="your_filter"`.
+This can be overridden via build property: `dotnet build build.proj -p:FilterStatement="your_filter"`.
 
 ### Test Attributes
 ```csharp
@@ -137,19 +137,19 @@ public void TestIntermittentlyFails() { ... }
 
 ## Running Tests
 
-### Using MSBuild (Recommended)
+### Using `dotnet build` (Recommended)
 ```bash
 # Build and run all unit tests
-msbuild -t:RunUnitTests
+dotnet build build.proj -t:RunUnitTests
 
 # Run functional tests only
-msbuild -t:RunFunctionalTests
+dotnet build build.proj -t:RunFunctionalTests
 
 # Run manual tests for specific framework
-msbuild -t:RunManualTests -p:TF=net8.0
+dotnet build build.proj -t:RunManualTests -p:TF=net8.0
 
 # Run specific test set
-msbuild -t:RunManualTests -p:TestSet=1
+dotnet build build.proj -t:RunManualTests -p:TestSet=1
 ```
 
 ### Using dotnet CLI
@@ -323,7 +323,7 @@ AssertExtensions.ThrowsContains<SqlException>(() => action(), "expected message"
 
 ### Running with Coverage
 ```bash
-msbuild -t:RunTests -p:CollectCoverage=true
+dotnet build build.proj -t:RunTests -p:CollectCoverage=true
 ```
 
 ### Coverage Targets
@@ -333,16 +333,11 @@ msbuild -t:RunTests -p:CollectCoverage=true
 
 ## Debugging Tests
 
-### Visual Studio
+### IDE
 1. Set breakpoints in test code
-2. Right-click test → Debug Test
+2. Right-click test → Debug Test (or use CodeLens "Debug Test" link)
 3. Use Test Explorer for navigation
 
-### VS Code
-1. Configure C# extension
-2. Use CodeLens "Debug Test" link
-3. Attach to test process
-
 ### Command Line
 ```bash
 # Enable verbose output

.github/plans/apicompat-ref-assembly-validation.md

@@ -9,7 +9,7 @@ The comparison uses `Microsoft.DotNet.ApiCompat.Tool` in **strict mode**, which
 ## Usage
 
 ```
-dotnet msbuild build.proj /t:CompareRefAssemblies /p:BaselinePackageVersion=6.1.4
+dotnet build build.proj /t:CompareRefAssemblies /p:BaselinePackageVersion=6.1.4
 ```
 
 - `BaselinePackageVersion` is **required** (no default). The user must specify which published package to compare against.
@@ -111,7 +111,7 @@ Add one line after the existing `.targets` imports (after line 7):
 ## Verification
 
 ```
-dotnet msbuild build.proj /t:CompareRefAssemblies /p:BaselinePackageVersion=6.1.4
+dotnet build build.proj /t:CompareRefAssemblies /p:BaselinePackageVersion=6.1.4
 ```
 
 - Downloads 6.1.4 nupkg, builds both ref project variants, runs 8 comparisons (4 TFMs × 2 variants).

BUILDGUIDE.md

@@ -6,20 +6,15 @@ This document provides all the necessary details to build the driver and run tes
 
 ### .NET SDK
 
-The projects in this repo require the .NET 10.0 SDK to build.  Please ensure you
-have the latest version of that SDK installed.
+The projects in this repo require the .NET 10.0 SDK to build and test.  Please ensure you have the
+latest version of that SDK installed.
 
-Tests and tools may require different .NET Runtimes that may be installed
-independently.  For example, tests targeting .NET 8.0 will need that runtime
-installed.
+Tests and tools may require different .NET Runtimes that may be installed independently.  For
+example, tests targeting .NET 8.0 will need that runtime installed.
 
-### Visual Studio
+### PowerShell
 
-This project should be built with Visual Studio 2019+ for the best compatibility. The required set of components are provided in the below file:
-
-- **Visual Studio 2019** with imported components: [VS19Components](/tools/vsconfig/VS19Components.vsconfig)
-
-- **Powershell**: To build SqlClient on Linux, powershell is needed as well. Follow the distro specific instructions at [Install Powershell on Linux](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.4)
+To build SqlClient on Linux, PowerShell is needed. Follow the distro specific instructions at [Install PowerShell on Linux](https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.4)
 
 Once the environment is setup properly, execute the desired set of commands below from the _root_ folder to perform the respective operations:
 
@@ -57,7 +52,7 @@ Manual Tests require the below setup to run:
   |IsManagedInstance | (Optional) When set to `true` **TVP** related tests will use non-Azure bsl files to compare test results. This is needed when testing against Azure Managed Instances; otherwise TVP Tests will fail on TestSet 3. The default value is `false`. |
   |PowerShellPath | The full path to PowerShell.exe. This is not required if the path is present in the PATH environment variable. | `D:\\escaped\\absolute\\path\\to\\PowerShell.exe` |
 
-## MSBuild Reference
+## Build Reference
 
 ### Targets
 
@@ -87,7 +82,7 @@ The following build targets are defined in `build.proj`:
 
 ### Parameters
 
-The following parameters may be defined as MSBuild properties to configure the
+The following parameters may be defined as properties to configure the
 build:
 
 |Name|Supported Values|Default|Description|
@@ -100,43 +95,43 @@ build:
 |`TF`|`net8.0`, `net462`, `net47`, `net471`, `net472`, `net48`, `net481`|`net9.0` in netcore, `net462` in netfx|Sets the target framework when building or running tests. Not applicable when building the drivers.|
 |`ResultsDirectory`|An absolute file path|./TestResults relative to current directory|Specifies where to write test results.|
 
-## Example Commands to Run Tests Using MSBuild (Recommended)
+## Example Commands to Run Tests Using `dotnet build` (Recommended)
 
 Using the default configuration and running all tests:
 
 ```bash
-msbuild -t:RunTests
+dotnet build build.proj -t:RunTests
 ```
 
 Using the Release configuration:
 
 ```bash
-msbuild -t:RunTests -p:Configuration=Release
+dotnet build build.proj -t:RunTests -p:Configuration=Release
 ```
 
 Running only the unit tests:
 
 ```bash
-msbuild -t:RunUnitTests
+dotnet build build.proj -t:RunUnitTests
 ```
 
 Using a specific .NET runtime to run tests:
 
 ```bash
-msbuild -t:RunTests -p:DotnetPath=C:\net8-win-x86\
+dotnet build build.proj -t:RunTests -p:DotnetPath=C:\net8-win-x86\
 ```
 
 To run tests against a specific version of .NET/.NET Framework, set the `-p:TF` parameter.
 
 ```bash
-msbuild -t:RunTests -p:TF=net8.0
-msbuild -t:RunTests -p:TF=net462
+dotnet build build.proj -t:RunTests -p:TF=net8.0
+dotnet build build.proj -t:RunTests -p:TF=net462
 ```
 
-## Example Commands to Run Tests using `dotnet`
+## Example Commands to Run Tests using `dotnet test`
 
-Under the hood, the MSBuild commands to run tests use `dotnet` commands. But, if you wish to run
-them without the overhead of wrapping/unwrapping in MSBuild, you can run them directly.
+Under the hood, the build targets to run tests use `dotnet test` commands. But, if you wish to run
+them without the overhead of the build.proj orchestration, you can run them directly.
 
 To change the processor architecture that runs the test (where possible, ie, x86 on x64), use the
 appropriate `dotnet` executable.
@@ -170,6 +165,7 @@ dotnet test "src/Microsoft.Data.SqlClient/tests/ManualTests/Microsoft.Data.SqlCl
 ```
 
 ### Run Unit Tests
+
 ```bash
 dotnet test "src/Microsoft.Data.SqlClient/tests/UnitTests/Microsoft.Data.SqlClient.UnitTests.csproj" \
   -p:Configuration=Release \
@@ -219,7 +215,6 @@ Provide property to `dotnet test` commands for testing desired reference type.
 dotnet test -p:ReferenceType=Project ...
 ```
 
-
 ## Using Managed SNI on Windows
 
 Managed SNI can be enabled on Windows by enabling the below AppContext switch:

doc/apps/AzureAuthentication/README.md

@@ -28,7 +28,7 @@ The app is designed to run against both **published NuGet packages** and **local
 
 ## Build Parameters
 
-Package versions are controlled through MSBuild properties. Pass them on the command line with `-p:`
+Package versions are controlled through build properties. Pass them on the command line with `-p:`
 (or `/p:`) to override the defaults defined in `Directory.Packages.props`.
 
 | Property | Default | Description |

eng/pipelines/common/templates/jobs/ci-build-nugets-job.yml

@@ -85,7 +85,6 @@ jobs:
     name: ${{parameters.poolName }}
     demands:
     - imageOverride -equals ${{ parameters.imageOverride }}
-    - msbuild
 
   variables:
     - template: /eng/pipelines/libraries/ci-build-variables.yml@self
@@ -176,15 +175,15 @@ jobs:
       mdsPackageVersion: ${{ parameters.mdsPackageVersion }}
       akvPackageVersion: ${{ parameters.akvPackageVersion }}
 
-  - task: MSBuild@1
+  - task: DotNetCoreCLI@2
     displayName: 'Create AKV Provider NuGet Package'
     inputs:
-      solution: build.proj
-      msbuildArchitecture: x64
-      platform: '${{ parameters.platform }}'
-      configuration: '${{ parameters.buildConfiguration }}'
-      msbuildArguments: >-
+      command: build
+      projects: build.proj
+      arguments: >-
         -t:PackAkvProvider
+        -p:Platform=${{ parameters.platform }}
+        -p:Configuration=${{ parameters.buildConfiguration }}
         -p:ReferenceType=${{ parameters.referenceType }}
         -p:LoggingPackageVersion=${{ parameters.loggingPackageVersion }}
         -p:MdsPackageVersion=${{ parameters.mdsPackageVersion }}

eng/pipelines/common/templates/steps/ci-project-build-step.yml

@@ -75,16 +75,15 @@ parameters:
 steps:
   # Build MDS
   - ${{ if or(eq(parameters.build, 'MDS'), eq(parameters.build, 'all'), eq(parameters.build, 'allNoDocs')) }}:
-    - task: MSBuild@1
+    - task: DotNetCoreCLI@2
       displayName: 'Build Driver'
       condition: and(succeeded(), eq(variables['Agent.OS'], 'Windows_NT'))
       inputs:
-        solution: build2.proj
-        msbuildArchitecture: x64
-        platform: '${{ parameters.platform }}'
-        configuration: '${{ parameters.buildConfiguration }}'
-        msbuildArguments:
+        command: build
+        projects: build2.proj
+        arguments: >-
           -t:BuildMds
+          -p:Configuration=${{ parameters.buildConfiguration }}
           -p:ReferenceType=${{ parameters.referenceType }}
           -p:BuildNumber=${{ parameters.assemblyBuildNumber }}
           -p:PackageVersionAbstractions=${{ parameters.abstractionsPackageVersion }}
@@ -93,16 +92,15 @@ steps:
 
   # Build AKV Provider
   - ${{ if or(eq(parameters.build, 'AkvProvider'), eq(parameters.build, 'all'), eq(parameters.build, 'allNoDocs')) }}:
-    - task: MSBuild@1
+    - task: DotNetCoreCLI@2
       displayName: 'Build AKV Provider'
       condition: and(succeeded(), eq(variables['Agent.OS'], 'Windows_NT'))
       inputs:
-        solution: build.proj
-        msbuildArchitecture: x64
-        platform: '${{ parameters.platform }}'
-        configuration: '${{ parameters.buildConfiguration }}'
-        msbuildArguments: >-
+        command: build
+        projects: build.proj
+        arguments: >-
           -t:BuildAkvProvider
+          -p:Platform=${{ parameters.platform }}
           -p:ReferenceType=${{ parameters.referenceType }}
           -p:TestEnabled=true
           -p:GenerateNuget=false
@@ -113,6 +111,3 @@ steps:
           -p:AbstractionsPackageVersion=${{ parameters.abstractionsPackageVersion }}
           -p:LoggingPackageVersion=${{ parameters.loggingPackageVersion }}
           -p:MdsPackageVersion=${{ parameters.mdsPackageVersion }}
-        verbosityRestore: Detailed
-        verbosityPack: Detailed
-