chore: add Revit 2027 support and GitHub Packages NuGet source#96
Conversation
Agent-Logs-Url: https://github.com/johnpierson/RhythmForDynamo/sessions/6ff4f75e-5d25-4d4c-a595-611398540eb8 Co-authored-by: johnpierson <15744724+johnpierson@users.noreply.github.com>
|
@copilot - can we revise all DynamoRevit dll references to use this nuget package source? https://github.com/johnpierson/DynamoVisualProgramming.Revit/pkgs/nuget/DynamoVisualProgramming.Revit |
…evit Agent-Logs-Url: https://github.com/johnpierson/RhythmForDynamo/sessions/951984bd-fdc3-4c56-af53-052899e3822b Co-authored-by: johnpierson <15744724+johnpierson@users.noreply.github.com>
Done in commit 2081c3b. Added a |
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