Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR adds support for Visual Studio 2026 to the MiKo-Analyzers project by creating new project variants and updating package dependencies to accommodate the next major version of Visual Studio.
Key Changes:
- Created new VS2026-specific project files (MiKo.Analyzer.2026, MiKo.Analyzer.CodeFixes.2026, MiKo.Analyzer.Package.2026, MiKo.Analyzer.Vsix2026)
- Updated package references to Roslyn 5.0 preview and .NET 10.0
- Extended conditional compilation directives throughout shared code to include VS2026 support
Reviewed Changes
Copilot reviewed 38 out of 38 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| appveyor.yml | Updated CI build image from VS2022 to VS2026 |
| README.md | Updated documentation to include VS2026 support |
| MiKo.Analyzer.sln | Added new VS2026 projects to solution structure |
| MiKo.Analyzer.Vsix2026/* | New VSIX extension project for VS2026 |
| MiKo.Analyzer.Package.2026/* | New NuGet package project for VS2026 |
| MiKo.Analyzer.Codefixes.2026/* | New code fixes project for VS2026 |
| MiKo.Analyzer.2026/* | New analyzer project for VS2026 |
| MiKo.Analyzer.Tests/MiKo.Analyzer.Tests.csproj | Updated test framework to .NET 10.0 |
| MiKo.Analyzer.Shared/* | Extended conditional compilation to support both VS2022 and VS2026 |
| MiKo.Analyzer.2022/* | Updated package version constraints to use version ranges |
| BenchmarkConsole/BenchmarkConsole.csproj | Updated Roslyn package to 5.0 preview |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
(due to added support for VS2026)
…Sharp.Workspaces' to v5.0.0
the 'shared' project get analyzed, so we avoid duplicates here (see https://learn.microsoft.com/de-de/visualstudio/code-quality/disable-code-analysis?view=visualstudio)
RalfKoban
added
the
waiting for 3rd party
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 47 out of 47 changed files in this pull request and generated 6 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| <ItemGroup> | ||
| <ProjectReference Include="..\MiKo.Analyzer.2026\MiKo.Analyzer.2026.csproj" /> | ||
| <ProjectReference Include="..\MiKo.Analyzer.Codefixes.2026\MiKo.Analyzer.Codefixes.2026.csproj" /> |
There was a problem hiding this comment.
The 2026 package project references a CodeFixes csproj path that does not exist in the repo (the actual file is MiKo.Analyzer.CodeFixes.2026.csproj with capital F). This will break builds on case-sensitive file systems and tooling that validates project references. Update the ProjectReference to match the real filename.
| <ProjectReference Include="..\MiKo.Analyzer.Codefixes.2026\MiKo.Analyzer.Codefixes.2026.csproj" /> | |
| <ProjectReference Include="..\MiKo.Analyzer.CodeFixes.2026\MiKo.Analyzer.CodeFixes.2026.csproj" /> |
RalfKoban
removed
the
waiting for 3rd party
Add support for Visual Studio 2026
Switch test project to .NET 10
(resolves #1515)