Skip to content

Add Visual Studio 2026 build support - #1067

Merged
jasonleenaylor merged 2 commits into
mainfrom
support-vs2026-builds
Aug 14, 2026
Merged

Add Visual Studio 2026 build support#1067
jasonleenaylor merged 2 commits into
mainfrom
support-vs2026-builds

Conversation

@jasonleenaylor

@jasonleenaylor jasonleenaylor commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

FieldWorks now builds with Visual Studio 2026 or 2022, preferring the newest installed. VS 2026 builds use its MSVC toolset; VS 2022 builds are unchanged.

Quick Summary

Merge ready checklist

  • Someone else has installed 2026 and built and run FieldWorks successfully

This change is Reviewable

FieldWorks now builds with Visual Studio 2026 or 2022, preferring the
newest installed. VS 2026 builds use its MSVC toolset; VS 2022 builds
are unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 14, 2026

Copy link
Copy Markdown

NUnit Tests

    1 files  ±0      1 suites  ±0   12m 4s ⏱️ +29s
5 760 tests ±0  5 679 ✅ ±0  81 💤 ±0  0 ❌ ±0 
5 769 runs  ±0  5 688 ✅ ±0  81 💤 ±0  0 ❌ ±0 

Results for commit baa4920. ± Comparison against base commit f2fac18.

♻️ This comment has been updated with latest results.

@codecov-commenter

codecov-commenter commented Aug 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 40.32%. Comparing base (1ada9f6) to head (baa4920).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1067      +/-   ##
==========================================
+ Coverage   36.44%   40.32%   +3.88%     
==========================================
  Files        1354     1542     +188     
  Lines      295692   365064   +69372     
  Branches    40228    40231       +3     
==========================================
+ Hits       107752   147228   +39476     
- Misses     158660   188551   +29891     
- Partials    29280    29285       +5     

see 223 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jtmaxwell3 jtmaxwell3 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jtmaxwell3 reviewed 20 files and all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on jasonleenaylor).

Build and setup scripts reported only a version number, so it was hard to
tell whether a build used Visual Studio 2026 or 2022 -- especially since
VS 2022 reports a display version such as "17.14.37 (July 2026)". They now
lead with the product name and also report the MSVC toolset.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@jasonleenaylor
jasonleenaylor merged commit f17ee34 into main Aug 14, 2026
6 of 7 checks passed
@jasonleenaylor
jasonleenaylor deleted the support-vs2026-builds branch August 14, 2026 21:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants