microsoft / microsoft/upgrade-agent-plugins
Upgrade Agent misses prerelease Visual Studio instances and falsely reports WebApplication tooling missing
@abpiskunov is already working on this.
Since Aug 25, 2026.
- Dominant language
- PowerShell
- Stars
- 37
- Forks
- 8
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 6
Description
Summary
Upgrade Agent reported that Visual Studio, the Web Application workload, .NET Framework targeting support, and Microsoft.WebApplication.targets were missing.
The machine had multiple complete prerelease Visual Studio installations with MSBuild and Microsoft.WebApplication.targets available.
Observed with: Upgrade Agent 1.1.404, GitHub Copilot App 1.1.10, Windows
Reproduction
- Install a prerelease Visual Studio instance, such as Insiders or Preview, with ASP.NET/Web Application build support.
- Run Upgrade Agent against a legacy ASP.NET Framework Web Application Project.
- Example repo to use: ContosoUniversity source: https://github.com/Azure-Samples/dotnet-migration-copilot-samples/tree/main/ContosoUniversity
- Ask it to assess baseline restore and build viability.
Actual result
Upgrade Agent:
- did not discover the prerelease Visual Studio instances
- used the .NET SDK’s bundled MSBuild
- failed with
MSB4019for missingMicrosoft.WebApplication.targets - classified the failure as an environment/setup blocker
- recommended installing tooling that was already present
Expected result
Upgrade Agent should:
- Discover stable and prerelease Visual Studio instances.
- Inspect each instance for MSBuild, required workloads, targeting packs, and target files.
- Select the newest complete compatible installation.
- Report missing tooling only after checking all eligible instances.
For example, vswhere requires -prerelease to include prerelease installations:
vswhere.exe -all -products * -prerelease
Contributor guide
No contributing guide indexed for this repository
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.