You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rhythm lacked build configurations and CI pipeline support for Revit 2027, though deploy/2027/ pre-built DLLs and the dynamo_to_revit_mapping.json entry ("4.0": [27]) were already in place.
Extended verification arrays to include 2026 and 2027 for both RhythmCore and RhythmRevit checks
Added an "Authenticate GitHub Packages NuGet source" step using GITHUB_TOKEN so MSBuild can restore DynamoVisualProgramming.Revit from the custom feed
NuGet source (NuGet.Config)
Added NuGet.Config at the repository root registering https://nuget.pkg.github.com/johnpierson/index.json as a package source alongside nuget.org, so that DynamoVisualProgramming.Revit is resolved from the custom GitHub Packages feed
Added a NuGet.Config at the repository root that registers https://nuget.pkg.github.com/johnpierson/index.json as a NuGet source (alongside nuget.org). Added an "Authenticate GitHub Packages NuGet source" step in build.yml that calls dotnet nuget update source with GITHUB_TOKEN so MSBuild can authenticate and restore DynamoVisualProgramming.Revit from that feed during all build steps.
CopilotAI
changed the title
chore: add Revit 2027 support
chore: add Revit 2027 support and GitHub Packages NuGet source
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rhythm lacked build configurations and CI pipeline support for Revit 2027, though
deploy/2027/pre-built DLLs and thedynamo_to_revit_mapping.jsonentry ("4.0": [27]) were already in place.Project configurations (
RhythmCore,RhythmRevit,RhythmUI)Debug R27/Release R27property groups to all three.csprojfiles4.0, target framework:net8.0-windows, define constants includeR27andR27_OR_GREATERItemGroupblocks to include/exclude R27 appropriatelyRhythmRevit2027 hint path reference inRhythmUI.csprojRhythmCore.csprojR26 was usingnet7.0-windows; updated tonet8.0-windowsto matchRhythmRevitandRhythmUISolution files
Debug R27|Any CPUandRelease R27|Any CPUtoSolutionConfigurationPlatformsandProjectConfigurationPlatformsin all three.slnfilesCI workflow (
build.yml)Build RhythmCore - Release R26step (was never building R26 core)Build RhythmCore - Release R27andBuild RhythmRevit - Release R27steps2026and2027for both RhythmCore and RhythmRevit checksGITHUB_TOKENso MSBuild can restoreDynamoVisualProgramming.Revitfrom the custom feedNuGet source (
NuGet.Config)NuGet.Configat the repository root registeringhttps://nuget.pkg.github.com/johnpierson/index.jsonas a package source alongsidenuget.org, so thatDynamoVisualProgramming.Revitis resolved from the custom GitHub Packages feed