Make PTVS build for Dev18
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.6k
- Forks
- 680
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
-
Update Source Code Build Configuration for Dev18
- Build Configuration Files
- C++ Project Files (vcxproj files)
- C# Project Files (.csproj files)
- Package Configuration
- Assembly Version Files
- VSIX Manifest
-
Build Pipelines: Update azure-pipelines.yml, release, and compliance pipeline configurations.
The current build pipeline uses the
MSBuild@1Azure task, which doesn't yet support Dev18. While the MSBuild command-line tool already supports Dev18 builds, we're waiting for Azure Pipeline task support.Track progress at https://github.com/microsoft/azure-pipelines-tasks/issues/21319
-
Update VS Bootstrapper Configuration
The build pipeline currently generates a Dev17 Visual Studio installer with the latest PTVS changes for testing purposes. This needs to be updated for Dev18.
- Update create_vs_bootstrapper.yml
- Coordinate with CTI: Notify the team that the bootstrapper will now generate Dev18 installer bits instead of Dev17
-
Snap PTVS Main to Dev17 Release Branch
- Create branch protection rules for the release branch
Currently, all changes flowing into Visual Studio main are targeting Dev18. Since the VS team has already snapped their main branch to the Dev17 release branch, we should also create a clear separation between Dev17 and Dev18 development streams.
This maintains stable Dev17 releases and also enables parallel Dev18 development.
-
Update the Build and Debug Instructions for PTVS: https://github.com/microsoft/PTVS/wiki/Build-and-Debug-Instructions-for-PTVS
-
Address Dev18-Specific Issues
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.