From 44d23600656af2801cd3b369ba4d7c30cb43bd6e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 13 Oct 2025 20:23:29 +0000 Subject: [PATCH 01/10] Initial plan From 6afa6f1a3be1cf66b66b268c5e4fcf1f66511188 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 13 Oct 2025 20:28:30 +0000 Subject: [PATCH 02/10] Add preview branch preparation documentation Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- README.md | 5 ++ doc/preview-branch-preparation.md | 126 ++++++++++++++++++++++++++++++ 2 files changed, 131 insertions(+) create mode 100644 doc/preview-branch-preparation.md diff --git a/README.md b/README.md index cc3824080..bc7f64cd2 100644 --- a/README.md +++ b/README.md @@ -2,6 +2,11 @@ This repository contains the version information for .NET SDK Workloads. +### Documentation + +- [Release Process](doc/release-process.md) - Current and ideal release process for workloads +- [Preview Branch Preparation](doc/preview-branch-preparation.md) - Process for preparing branches during preview releases + ### Pre-requisites for local VS insertion build 1. Install the latest [Visual Studio](https://visualstudio.microsoft.com/downloads/) with the .NET Desktop workload diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md new file mode 100644 index 000000000..b8908d039 --- /dev/null +++ b/doc/preview-branch-preparation.md @@ -0,0 +1,126 @@ +# Preview Branch Preparation Process + +This document outlines the process we go through during previews to prepare the branches for a workloads insertion. + +## Overview + +When preparing for a new preview release of .NET, we need to ensure that the workload-versions repository is properly configured to receive and flow dependencies from the correct sources. This involves updating Maestro subscriptions to point to the appropriate channels for the preview period. + +## Process Steps + +### 1. Change the Channel for the dotnet/dotnet Subscription + +The workload-versions repository receives dependencies from the `dotnet/dotnet` repository (the VMR - Virtual Monolithic Repository) through Maestro subscriptions. During preview periods, we need to update these subscriptions to point to the correct preview channel. + +#### Steps to Update the Subscription: + +1. **Identify the target preview channel** + - Preview channels typically follow the pattern: `.NET Preview ` + - Example: `.NET 10 Preview 1`, `.NET 10 Preview 2`, etc. + - You can list available channels using: `darc get-channels` + +2. **Find the current subscription** + - List all subscriptions for the repository: + ```bash + darc get-subscriptions --target-repo workload-versions + ``` + - Identify the subscription from `dotnet/dotnet` (the VMR) + +3. **Update the subscription to the new preview channel** + - Use the DARC tool to update the subscription: + ```bash + darc update-subscription --id --channel "" + ``` + - Example: + ```bash + darc update-subscription --id 12345 --channel ".NET 10 Preview 2" + ``` + +4. **Verify the subscription update** + - Confirm the change was applied: + ```bash + darc get-subscription --id + ``` + - Check that the `Channel` field shows the new preview channel + +5. **Monitor dependency flow** + - After updating the subscription, monitor for new pull requests from Maestro + - PRs will be automatically created when new builds are published to the preview channel + - These PRs will update the `eng/Version.Details.xml` file with new dependency versions + +### 2. Update Branch Configuration + +Depending on the preview and SDK version you're preparing for, you may need to: + +1. **Create or update the appropriate branch** + - For example: `release/10.0.1xx-preview2` for .NET 10 Preview 2 SDK band 100 + - Ensure the branch is created from the correct starting point + +2. **Update Version.props** + - Set the appropriate version features and patch levels for the preview + - Update `VersionFeature` to match the SDK release band + - Ensure `VersionPatch` is set correctly (typically 0 for a new preview) + +3. **Configure channel publishing** + - Ensure builds from this branch publish to the correct workloads feed + - For .NET 10: `dotnet10-workloads` feed + - Feed URL: `https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet10-workloads/nuget/v3/index.json` + +## Reference Information + +### Workloads Feeds by .NET Version + +- dotnet8-workloads: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8-workloads/nuget/v3/index.json +- dotnet9-workloads: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet9-workloads/nuget/v3/index.json +- dotnet10-workloads: https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet10-workloads/nuget/v3/index.json + +### Useful DARC Commands + +```bash +# List all channels +darc get-channels + +# List subscriptions for this repository +darc get-subscriptions --target-repo workload-versions + +# Get details of a specific subscription +darc get-subscription --id + +# Update a subscription's channel +darc update-subscription --id --channel "" + +# List available builds in a channel +darc get-builds --channel "" +``` + +### Documentation Links + +- [DARC Documentation](https://github.com/dotnet/arcade/blob/main/Documentation/Darc.md) +- [Maestro/Dependency Flow Documentation](https://github.com/dotnet/arcade/blob/main/Documentation/DependencyFlowOnboarding.md) +- [Release Process Documentation](release-process.md) + +## Common Issues and Troubleshooting + +### Subscription Not Updating + +If dependency PRs are not being created after updating the subscription: + +1. Verify the subscription channel is correct +2. Check that builds are being published to the target channel +3. Ensure the subscription is enabled (not disabled) +4. Check Maestro for any errors in the subscription processing + +### Wrong Dependencies Flowing In + +If you're receiving dependencies from the wrong builds: + +1. Verify the subscription is pointing to the correct channel +2. Check the channel's build sources +3. Ensure you updated the correct subscription (there may be multiple) + +## Timeline Considerations + +- Subscription channel updates should be made **before** the first preview build is published +- Allow time for the first dependency update PR to flow through and be merged +- Coordinate with the dotnet/dotnet (VMR) team on preview build schedules +- Plan for at least one full dependency flow cycle before declaring the branch ready for insertions From ff02916c1f563880694893cd095b0a00d33894c4 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Mon, 13 Oct 2025 20:34:48 +0000 Subject: [PATCH 03/10] Add MAUI package ID and VS manifest update steps to preview documentation Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 71 +++++++++++++++++++++++++++++++ 1 file changed, 71 insertions(+) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index b8908d039..c667d6a0f 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -66,6 +66,77 @@ Depending on the preview and SDK version you're preparing for, you may need to: - For .NET 10: `dotnet10-workloads` feed - Feed URL: `https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet10-workloads/nuget/v3/index.json` +### 3. Update Package IDs for MAUI Packages + +When transitioning to a new preview, you need to update the package ID suffixes for all MAUI-related packages in `eng/Versions.props`. + +#### Steps to Update MAUI Package IDs: + +1. **Locate the MauiWorkloads property group** + - Open `eng/Versions.props` + - Find the `` section + +2. **Update the MauiFeatureBand property** + - Change to match the new preview version + - Example: `10.0.100-rc.3` + +3. **Update all MAUI manifest package property names** + - The property names encode the SDK band and preview in their suffix + - For example, when moving from RC 2 to RC 3: + - `MicrosoftNETSdkAndroidManifest100100rc2PackageVersion` → `MicrosoftNETSdkAndroidManifest100100rc3PackageVersion` + - `MicrosoftNETSdkiOSManifest100100rc2PackageVersion` → `MicrosoftNETSdkiOSManifest100100rc3PackageVersion` + - `MicrosoftNETSdktvOSManifest100100rc2PackageVersion` → `MicrosoftNETSdktvOSManifest100100rc3PackageVersion` + - `MicrosoftNETSdkMacCatalystManifest100100rc2PackageVersion` → `MicrosoftNETSdkMacCatalystManifest100100rc3PackageVersion` + - `MicrosoftNETSdkmacOSManifest100100rc2PackageVersion` → `MicrosoftNETSdkmacOSManifest100100rc3PackageVersion` + - `MicrosoftNETSdkMauiManifest100100rc2PackageVersion` → `MicrosoftNETSdkMauiManifest100100rc3PackageVersion` + +4. **Update the references to these properties** + - Update property references in the assignment statements: + ```xml + $(MicrosoftNETSdkMauiManifest100100rc3PackageVersion) + $(MicrosoftNETSdkAndroidManifest100100rc3PackageVersion) + + ``` + +5. **Verify all package property names are updated consistently** + - Ensure the suffix pattern matches across all MAUI workload packages + - The pattern should be: `{Major}{Minor}{Band}{PreviewLabel}{PreviewNumber}` + - Example: `100100rc3` represents 10.0.100-rc.3 + +### 4. Update VS Manifest IDs for Mono and Emsdk Workloads + +Visual Studio integration requires updating the VSMAN (Visual Studio Manifest) IDs and external.vsmanproj references for mono and emsdk workloads when preparing for a new preview. + +#### Steps to Update VS Manifest Configuration: + +1. **Update VSMAN IDs** + - The VSMAN IDs need to be updated to match the new preview version + - These IDs are typically referenced in Visual Studio insertion configuration + - Coordinate with the VS insertion team to ensure the correct VSMAN ID format for the preview + +2. **Update external.vsmanproj for mono workload** + - Locate or create the external.vsmanproj file for the mono workload + - Update any version-specific identifiers to match the new preview + - Ensure the ComponentId reflects the correct preview version + +3. **Update external.vsmanproj for emsdk workload** + - Similarly, update the external.vsmanproj file for the emsdk (Emscripten) workload + - Update version identifiers and component references + - Verify the ComponentId aligns with the new preview numbering + +4. **Verify VSMAN SDK version** + - Check `global.json` for the `Microsoft.VisualStudio.Internal.MicroBuild.Vsman` version + - Ensure it's compatible with the preview release + - Update if necessary to the latest version + +5. **Coordinate with VS insertion process** + - The VS insertion pipeline may need configuration updates for the new preview + - Ensure the VSMAN package generation is set up for the correct preview channel + - Test the insertion process with a test build before the official preview release + +> [!NOTE] +> The exact location and format of VSMAN configuration files may vary based on the repository structure and VS insertion setup. Coordinate with the Visual Studio integration team for specific requirements for your preview release. + ## Reference Information ### Workloads Feeds by .NET Version From 21630a4f8d8fc95c4c4558dee8557d65f5f857d6 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 14 Oct 2025 22:09:27 +0000 Subject: [PATCH 04/10] Add source-repo and target-branch parameters to darc get-subscriptions command Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index c667d6a0f..42944beb7 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -22,7 +22,7 @@ The workload-versions repository receives dependencies from the `dotnet/dotnet` 2. **Find the current subscription** - List all subscriptions for the repository: ```bash - darc get-subscriptions --target-repo workload-versions + darc get-subscriptions --target-repo workload-versions --source-repo dotnet/dotnet --target-branch main ``` - Identify the subscription from `dotnet/dotnet` (the VMR) From 09cf4b00fe57a71f8d95053678eda7508dd96de9 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 14 Oct 2025 22:12:05 +0000 Subject: [PATCH 05/10] Clarify that major version previews are shipped from main branch Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index 42944beb7..6f656dadb 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -50,11 +50,11 @@ The workload-versions repository receives dependencies from the `dotnet/dotnet` ### 2. Update Branch Configuration -Depending on the preview and SDK version you're preparing for, you may need to: +For major version previews shipped from the main branch: -1. **Create or update the appropriate branch** - - For example: `release/10.0.1xx-preview2` for .NET 10 Preview 2 SDK band 100 - - Ensure the branch is created from the correct starting point +1. **Work from the main branch** + - Major version previews (e.g., .NET 10 RC 1, RC 2) are typically shipped from the main branch + - No separate preview branch is needed for these releases 2. **Update Version.props** - Set the appropriate version features and patch levels for the preview From 0126fa0bb1a16e056462f07d191e0d499aef58ea Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 14 Oct 2025 23:20:08 +0000 Subject: [PATCH 06/10] =?UTF-8?q?Update=20MAUI=20package=20ID=20examples?= =?UTF-8?q?=20from=20RC=202=E2=86=923=20to=20RC=201=E2=86=922?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index 6f656dadb..4d34c4a25 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -78,30 +78,30 @@ When transitioning to a new preview, you need to update the package ID suffixes 2. **Update the MauiFeatureBand property** - Change to match the new preview version - - Example: `10.0.100-rc.3` + - Example: `10.0.100-rc.2` 3. **Update all MAUI manifest package property names** - The property names encode the SDK band and preview in their suffix - - For example, when moving from RC 2 to RC 3: - - `MicrosoftNETSdkAndroidManifest100100rc2PackageVersion` → `MicrosoftNETSdkAndroidManifest100100rc3PackageVersion` - - `MicrosoftNETSdkiOSManifest100100rc2PackageVersion` → `MicrosoftNETSdkiOSManifest100100rc3PackageVersion` - - `MicrosoftNETSdktvOSManifest100100rc2PackageVersion` → `MicrosoftNETSdktvOSManifest100100rc3PackageVersion` - - `MicrosoftNETSdkMacCatalystManifest100100rc2PackageVersion` → `MicrosoftNETSdkMacCatalystManifest100100rc3PackageVersion` - - `MicrosoftNETSdkmacOSManifest100100rc2PackageVersion` → `MicrosoftNETSdkmacOSManifest100100rc3PackageVersion` - - `MicrosoftNETSdkMauiManifest100100rc2PackageVersion` → `MicrosoftNETSdkMauiManifest100100rc3PackageVersion` + - For example, when moving from RC 1 to RC 2: + - `MicrosoftNETSdkAndroidManifest100100rc1PackageVersion` → `MicrosoftNETSdkAndroidManifest100100rc2PackageVersion` + - `MicrosoftNETSdkiOSManifest100100rc1PackageVersion` → `MicrosoftNETSdkiOSManifest100100rc2PackageVersion` + - `MicrosoftNETSdktvOSManifest100100rc1PackageVersion` → `MicrosoftNETSdktvOSManifest100100rc2PackageVersion` + - `MicrosoftNETSdkMacCatalystManifest100100rc1PackageVersion` → `MicrosoftNETSdkMacCatalystManifest100100rc2PackageVersion` + - `MicrosoftNETSdkmacOSManifest100100rc1PackageVersion` → `MicrosoftNETSdkmacOSManifest100100rc2PackageVersion` + - `MicrosoftNETSdkMauiManifest100100rc1PackageVersion` → `MicrosoftNETSdkMauiManifest100100rc2PackageVersion` 4. **Update the references to these properties** - Update property references in the assignment statements: ```xml - $(MicrosoftNETSdkMauiManifest100100rc3PackageVersion) - $(MicrosoftNETSdkAndroidManifest100100rc3PackageVersion) + $(MicrosoftNETSdkMauiManifest100100rc2PackageVersion) + $(MicrosoftNETSdkAndroidManifest100100rc2PackageVersion) ``` 5. **Verify all package property names are updated consistently** - Ensure the suffix pattern matches across all MAUI workload packages - The pattern should be: `{Major}{Minor}{Band}{PreviewLabel}{PreviewNumber}` - - Example: `100100rc3` represents 10.0.100-rc.3 + - Example: `100100rc2` represents 10.0.100-rc.2 ### 4. Update VS Manifest IDs for Mono and Emsdk Workloads From 46b140ee5aebde84d1a2df3232653799fec7ef60 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Tue, 14 Oct 2025 23:22:50 +0000 Subject: [PATCH 07/10] Update VS manifest documentation with specific file names Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index 4d34c4a25..552767a40 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -109,18 +109,19 @@ Visual Studio integration requires updating the VSMAN (Visual Studio Manifest) I #### Steps to Update VS Manifest Configuration: -1. **Update VSMAN IDs** +1. **Update VSMAN IDs in dotnet-workloads-components.json** - The VSMAN IDs need to be updated to match the new preview version - - These IDs are typically referenced in Visual Studio insertion configuration + - These IDs are referenced in `dotnet-workloads-components.json` + - Update the VSMAN references for mono and emsdk workloads in this configuration file - Coordinate with the VS insertion team to ensure the correct VSMAN ID format for the preview -2. **Update external.vsmanproj for mono workload** - - Locate or create the external.vsmanproj file for the mono workload +2. **Update VisualStudio.External.vsmanproj for mono workload** + - Locate the `VisualStudio.External.vsmanproj` file for the mono workload - Update any version-specific identifiers to match the new preview - Ensure the ComponentId reflects the correct preview version -3. **Update external.vsmanproj for emsdk workload** - - Similarly, update the external.vsmanproj file for the emsdk (Emscripten) workload +3. **Update VisualStudio.External.vsmanproj for emsdk workload** + - Similarly, update the `VisualStudio.External.vsmanproj` file for the emsdk (Emscripten) workload - Update version identifiers and component references - Verify the ComponentId aligns with the new preview numbering From d2cb49916a307743a949008d2e692d79e786f1a4 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 17 Oct 2025 20:58:12 +0000 Subject: [PATCH 08/10] Add note about dotnet-dotnet subscription source for RC and servicing Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index 552767a40..b01e66503 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -25,6 +25,9 @@ The workload-versions repository receives dependencies from the `dotnet/dotnet` darc get-subscriptions --target-repo workload-versions --source-repo dotnet/dotnet --target-branch main ``` - Identify the subscription from `dotnet/dotnet` (the VMR) + + > [!NOTE] + > For RC1, RC2, and servicing releases, the subscription source is from `dotnet-dotnet` (the internal Azure DevOps URI: `https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet`). 3. **Update the subscription to the new preview channel** - Use the DARC tool to update the subscription: From 7c31d1e728d5c77acafd95f61f236906bde4f3de Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 17 Oct 2025 21:01:02 +0000 Subject: [PATCH 09/10] Update channel name format to include SDK and version details Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index b01e66503..1d37e8d38 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -15,8 +15,9 @@ The workload-versions repository receives dependencies from the `dotnet/dotnet` #### Steps to Update the Subscription: 1. **Identify the target preview channel** - - Preview channels typically follow the pattern: `.NET Preview ` - - Example: `.NET 10 Preview 1`, `.NET 10 Preview 2`, etc. + - Preview channels typically follow the pattern: `.NET .0.1xx SDK Preview ` + - Example: `.NET 10.0.1xx SDK Preview 1`, `.NET 10.0.1xx SDK Preview 2`, etc. + - For RC1, RC2, and servicing releases, the channel form is: `.NET .0.1xx SDK Internal` (for MSRC releases) - You can list available channels using: `darc get-channels` 2. **Find the current subscription** @@ -36,7 +37,7 @@ The workload-versions repository receives dependencies from the `dotnet/dotnet` ``` - Example: ```bash - darc update-subscription --id 12345 --channel ".NET 10 Preview 2" + darc update-subscription --id 12345 --channel ".NET 10.0.1xx SDK Preview 2" ``` 4. **Verify the subscription update** From f207b373043ebaa3e43d3e105ef93be21f7ea07b Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 17 Oct 2025 21:14:10 +0000 Subject: [PATCH 10/10] Remove VS team coordination references and VSMAN SDK version step Co-authored-by: marcpopMSFT <12663534+marcpopMSFT@users.noreply.github.com> --- doc/preview-branch-preparation.md | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/doc/preview-branch-preparation.md b/doc/preview-branch-preparation.md index 1d37e8d38..d89b4c6fc 100644 --- a/doc/preview-branch-preparation.md +++ b/doc/preview-branch-preparation.md @@ -117,7 +117,6 @@ Visual Studio integration requires updating the VSMAN (Visual Studio Manifest) I - The VSMAN IDs need to be updated to match the new preview version - These IDs are referenced in `dotnet-workloads-components.json` - Update the VSMAN references for mono and emsdk workloads in this configuration file - - Coordinate with the VS insertion team to ensure the correct VSMAN ID format for the preview 2. **Update VisualStudio.External.vsmanproj for mono workload** - Locate the `VisualStudio.External.vsmanproj` file for the mono workload @@ -129,18 +128,13 @@ Visual Studio integration requires updating the VSMAN (Visual Studio Manifest) I - Update version identifiers and component references - Verify the ComponentId aligns with the new preview numbering -4. **Verify VSMAN SDK version** - - Check `global.json` for the `Microsoft.VisualStudio.Internal.MicroBuild.Vsman` version - - Ensure it's compatible with the preview release - - Update if necessary to the latest version - -5. **Coordinate with VS insertion process** +4. **Coordinate with VS insertion process** - The VS insertion pipeline may need configuration updates for the new preview - Ensure the VSMAN package generation is set up for the correct preview channel - Test the insertion process with a test build before the official preview release > [!NOTE] -> The exact location and format of VSMAN configuration files may vary based on the repository structure and VS insertion setup. Coordinate with the Visual Studio integration team for specific requirements for your preview release. +> The exact location and format of VSMAN configuration files may vary based on the repository structure and VS insertion setup. ## Reference Information