菜单
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).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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).
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).
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).
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).
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).
Register and review .NET dependency-injection services and lifetimes on IServiceCollection. USE FOR: adding a registration, choosing singleton/scoped/transient, grouping registrations behind a feature extension, assembly scanning with Scrutor, or validating a service graph. DO NOT USE FOR: choosing which kind of type to declare (use designing-dotnet-types), or wiring the host builder and its lifecycle (use configuring-dotnet-hosting).
基于 SOC 职业分类
| name | revit-api-references |
| description | 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). |
| license | MIT |
The Nice3point.Revit.Api.* NuGet packages carry the Revit API assemblies; a project compiles for any Revit year without that year installed locally.
A local file (HintPath) reference ties the build to one installed version at one path and breaks CI and teammates' machines.
RevitAPI, RevitAPIUI, or another Revit-targeting assembly.
<PackageReference Include="Nice3point.Revit.Api.RevitAPI" Version="$(RevitVersion).*"/>
<PackageReference Include="Nice3point.Revit.Api.RevitAPIUI" Version="$(RevitVersion).*"/>
<PackageReference Include="Nice3point.Revit.Extensions" Version="2025.0.0" Condition="$(RevitVersion) == '2025'"/>
<PackageReference Include="Nice3point.Revit.Extensions" Version="2026.0.0" Condition="$(RevitVersion) == '2026'"/>
<PackageReference Include="Nice3point.Revit.Extensions" Version="2027.0.0" Condition="$(RevitVersion) == '2027'"/>
The $(RevitVersion).* wildcard resolves the assembly set for the active configuration.
$(RevitVersion) is supplied by the Nice3point.Revit.Sdk, which derives it from the build configuration (for example Release.R27 → 2027) — see revit-sdk-project-configuration.
The $(RevitVersion).* wildcard can be used for built-in API dependencies, they almost never have critical changes within a major version;
for all other dependencies, always use the exact package version to avoid breaking when the package is updated.
With central package management, pin the version in Directory.Packages.props.
Do not add a local file reference — it requires that exact Revit version at that exact path on every build machine:
<!-- BAD -->
<Reference Include="RevitAPI">
<HintPath>C:\Program Files\Autodesk\Revit 2027\RevitAPI.dll</HintPath>
</Reference>
Assemblies ship as Nice3point.Revit.Api.* with RevitAPI, RevitAPIUI, RevitAPIIFC, AdWindows, UIFramework, and more.
Check the Nice3point.Revit.Api.* packages before adding any assembly reference; only request a new one if it does not exist.
Restore and build on a machine (or CI) with no Revit installed.
Nice3point.Revit.Api.* packages.HintPath/local-file reference to a Revit DLL remains.$(RevitVersion).* wildcard (or central package management).| Pitfall | Correct approach |
|---|---|
<HintPath> to an installed Revit DLL | Use Nice3point.Revit.Api.* with $(RevitVersion).*. |
| A fixed API version that breaks other years | Use the $(RevitVersion).* wildcard. |
| An external NuGet package targets a floating version | Use the exact package version. |
| Copying a Revit DLL into the repo | Reference the NuGet package. |