Run any Skill in Manus with one click

revit-multi-version-configuration

Stars6

Forks1

UpdatedJuly 23, 2026 at 12:21

Support multiple Autodesk Revit versions in one project with Debug.RNN/Release.RNN configurations and REVIT#### conditional compilation. USE FOR: declaring the supported-version matrix, adding or removing a version, and writing #if REVIT####_OR_GREATER branches for genuine API differences. DO NOT USE FOR: what the SDK derives per version (use revit-sdk-project-configuration), or referencing the Revit API packages (use revit-api-references).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Nice3point

Nice3point/revit-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	revit-multi-version-configuration
description	Support multiple Autodesk Revit versions in one project with Debug.RNN/Release.RNN configurations and REVIT#### conditional compilation. USE FOR: declaring the supported-version matrix, adding or removing a version, and writing #if REVIT####_OR_GREATER branches for genuine API differences. DO NOT USE FOR: what the SDK derives per version (use revit-sdk-project-configuration), or referencing the Revit API packages (use revit-api-references).
license	MIT

Revit Multi-Version Configuration

A Revit project builds one configuration per supported year. The Nice3point.Revit.Sdk derives the framework and the cumulative REVIT#### / REVIT####_OR_GREATER symbols from the active Debug.RNN / Release.RNN configuration.

When to use

Declaring or changing which Revit years a project supports.
Writing version-specific code for a real API difference.

When not to use

Understanding what the SDK sets automatically per version — use revit-sdk-project-configuration.
Adding the Revit API assembly references — use revit-api-references.

Workflow

Step 1: Declare the configuration matrix

<Configurations>Debug.R25;Debug.R26;Debug.R27</Configurations>
<Configurations>$(Configurations);Release.R25;Release.R26;Release.R27</Configurations>

Mirror the same Debug.RNN/Release.RNN set in the .slnx/.sln file.

Step 2: Add or remove a version

Add or remove the matching Debug.RNN / Release.RNN in the solution and the project's <Configurations>. For a newly released year, first update the SDK; set TargetFramework explicitly only when the SDK is not released with the latest Revit version support or you are using the preview API package:

<TargetFramework Condition="$(RevitVersion) == '2027'">net10.0-windows7.0</TargetFramework>

Step 3: Add preprocessor directives for incompatible API

Write shared code first. Add a #if branch only where the Revit API genuinely differs; keep both branches independently compilable.

#if REVIT2024_OR_GREATER
    // API available from Revit 2024 onward
#else
    // legacy API
#endif

Step 4: Verify

Restore and build every declared configuration, and run version-specific tests for each branch that changed.

Validation

The active solution matrix selects the intended project Debug.RNN/Release.RNN configurations.
#if branches cover only genuine API differences, and both sides compile.
Every declared configuration restores and builds.

Common Pitfalls

Pitfall	Correct approach
Editing configurations through the IDE dialog	Edit `<Configurations>` in the `.csproj` by hand.
A `#if` around code that is identical on both sides	Keep it shared; branch only on real differences.
Solution and project matrices drifting apart	Keep both lists identical.
A branch that only compiles for one version	Ensure both `#if` sides build.

More from this repository

same repository

revit-utils-extensions

Nice3point/revit-skills

Replace verbose Autodesk Revit *Utils static calls, static managers, and hand-written enum/id conversions with Nice3point.Revit.Extensions fluent extensions. USE FOR: any time you need to call a SomeUtils.Operation(…) or any other static Revit API helper, and any time you convert or format a Revit value. DO NOT USE FOR: querying the model for elements (use revit-element-collector), or reading and writing element parameters (use revit-element-and-parameter-access).

2026-07-236

revit-addin-bundle

Nice3point/revit-skills

Package a versioned Autodesk Revit add-in as an Autodesk App Store bundle with the Nice3point.Revit.Templates ModularPipelines build. USE FOR: setting the bundle vendor metadata and version, and running the build to produce a versioned .bundle with per-Revit-year contents for App Store distribution. DO NOT USE FOR: per-build deploy or publish to a local Revit (use revit-addin-publishing), or launching and debugging (use revit-addin-debugging).

2026-07-236

revit-sdk-project-configuration

Nice3point/revit-skills

Configure the Revit project .csproj with the MSBuild Nice3point.Revit.Sdk. USE FOR: setting the project SDK, or configuring the target framework, implicit usings, language version, or add-in defaults. DO NOT USE FOR: adding or removing a supported Revit version (use revit-multi-version-configuration), referencing the Revit API assemblies (use revit-api-references), or publishing the add-in (use revit-addin-publishing).

2026-07-236

revit-command-and-application

Nice3point/revit-skills

Build Autodesk Revit add-in entry points with Nice3point.Revit.Toolkit base classes, not raw IExternalCommand/IExternalApplication interfaces. USE FOR: authoring an external command or application with a simplified Execute()/OnStartup() override, optional OnShutdown() override, ready context properties, and automatic dependency resolution. DO NOT USE FOR: dispatching API work from code that runs outside the Revit API context (use revit-external-events).

2026-07-236

revit-api-references

Nice3point/revit-skills

Reference the Autodesk Revit API assemblies using the Nice3point.Revit.Api.* or Nice3point toolkit, extensions or other NuGet packages. USE FOR: adding a Revit API assembly reference. DO NOT USE FOR: the version matrix and conditional compilation (use revit-multi-version-configuration).

2026-07-236

binding-and-validating-options

Nice3point/revit-skills

Bind a configuration section to a typed options class and validate it at startup with the .NET options pattern. USE FOR: adding an options type, binding it from configuration, applying DataAnnotations or custom validation, and failing fast on invalid configuration with ValidateOnStart. DO NOT USE FOR: general host composition and the order of builder extensions (use configuring-dotnet-hosting).

2026-07-236

name	revit-multi-version-configuration
description	Support multiple Autodesk Revit versions in one project with Debug.RNN/Release.RNN configurations and REVIT#### conditional compilation. USE FOR: declaring the supported-version matrix, adding or removing a version, and writing #if REVIT####_OR_GREATER branches for genuine API differences. DO NOT USE FOR: what the SDK derives per version (use revit-sdk-project-configuration), or referencing the Revit API packages (use revit-api-references).
license	MIT

Revit Multi-Version Configuration

When to use

Declaring or changing which Revit years a project supports.
Writing version-specific code for a real API difference.

When not to use

Understanding what the SDK sets automatically per version — use revit-sdk-project-configuration.
Adding the Revit API assembly references — use revit-api-references.

Workflow

Step 1: Declare the configuration matrix

<Configurations>Debug.R25;Debug.R26;Debug.R27</Configurations>
<Configurations>$(Configurations);Release.R25;Release.R26;Release.R27</Configurations>

Mirror the same Debug.RNN/Release.RNN set in the .slnx/.sln file.

Step 2: Add or remove a version

<TargetFramework Condition="$(RevitVersion) == '2027'">net10.0-windows7.0</TargetFramework>

Step 3: Add preprocessor directives for incompatible API

Write shared code first. Add a #if branch only where the Revit API genuinely differs; keep both branches independently compilable.

#if REVIT2024_OR_GREATER
    // API available from Revit 2024 onward
#else
    // legacy API
#endif

Step 4: Verify

Restore and build every declared configuration, and run version-specific tests for each branch that changed.

Validation

The active solution matrix selects the intended project Debug.RNN/Release.RNN configurations.
#if branches cover only genuine API differences, and both sides compile.
Every declared configuration restores and builds.

Common Pitfalls

Pitfall	Correct approach
Editing configurations through the IDE dialog	Edit `<Configurations>` in the `.csproj` by hand.
A `#if` around code that is identical on both sides	Keep it shared; branch only on real differences.
Solution and project matrices drifting apart	Keep both lists identical.
A branch that only compiles for one version	Ensure both `#if` sides build.