Run any Skill in Manus with one click

revit-addin-publishing

Stars6

Forks1

UpdatedJuly 23, 2026 at 12:21

Configure an Autodesk Revit add-in project to copy the add-in, .addin manifest to the local Revit or a `bin/publish` folder, using the Nice3point.Revit.Sdk publish targets. USE FOR: setting up a project for publishing, bundling extra content into the output, and relying on per-version manifest patching. DO NOT USE FOR: launching and debugging the add-in from the IDE (use revit-addin-debugging), dependency isolation or repacking (use revit-dependency-isolation), or packaging a versioned App Store bundle (use revit-addin-bundle).

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-addin-publishing
description	Configure an Autodesk Revit add-in project to copy the add-in, .addin manifest to the local Revit or a `bin/publish` folder, using the Nice3point.Revit.Sdk publish targets. USE FOR: setting up a project for publishing, bundling extra content into the output, and relying on per-version manifest patching. DO NOT USE FOR: launching and debugging the add-in from the IDE (use revit-addin-debugging), dependency isolation or repacking (use revit-dependency-isolation), or packaging a versioned App Store bundle (use revit-addin-bundle).
license	MIT

Revit Add-in Publishing

The Nice3point.Revit.Sdk targets copy the built add-in and its .addin manifest to one of two destinations and patch the manifest per Revit version. DeployAddin copies into the local Revit add-ins folder (%AppData%\Autodesk\Revit\Addins\<version>); the running Revit loads the add-in on its next start. PublishAddin copies into bin\publish (like dotnet publish) for distribution or the installer. Enable them only in the project that owns the .addin manifest.

When to use

Setting up a project to copy its add-in to the local Revit for testing, or to bin/publish for distribution.
Bundling extra content (families, resources) into the add-in output.

Workflow

Step 1: Deploy or publish

<DeployAddin>true</DeployAddin> <!-- to %AppData%\Autodesk\Revit\Addins\<version> -->
<PublishAddin>true</PublishAddin> <!-- to bin\publish for distribution -->

DeployAddin implies publishing. Override the targets with AddinDeployDir / AddinPublishDir.

Step 2: Include extra content

<Content Include="Families\**" PublishDirectory="Families" CopyToPublishDirectory="PreserveNewest"/>

Step 3: Rely on manifest patching

The SDK removes the ManifestSettings node for Revit versions older than 2027 during publish to support legacy Revit versions.

Step 4: Verify

Build, and confirm the add-in and manifest land in the deploy or publish folder and that Revit loads the add-in.

Validation

Deploy/publish is enabled only in the project holding the .addin manifest.
Extra content is declared with PublishDirectory / CopyToPublishDirectory.
The manifest works across supported years via SDK patching.

Common Pitfalls

Pitfall	Correct approach
Enabling deploy in a class-library project with no `.addin`	Enable it only in the manifest-owning project.
Copying families with a raw `<None>` item	Use `<Content … PublishDirectory=… CopyToPublishDirectory=…/>`.
Hand-editing the manifest per Revit version	Let the SDK patch `ManifestSettings` on publish.

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-addin-publishing
description	Configure an Autodesk Revit add-in project to copy the add-in, .addin manifest to the local Revit or a `bin/publish` folder, using the Nice3point.Revit.Sdk publish targets. USE FOR: setting up a project for publishing, bundling extra content into the output, and relying on per-version manifest patching. DO NOT USE FOR: launching and debugging the add-in from the IDE (use revit-addin-debugging), dependency isolation or repacking (use revit-dependency-isolation), or packaging a versioned App Store bundle (use revit-addin-bundle).
license	MIT

Revit Add-in Publishing

When to use

Setting up a project to copy its add-in to the local Revit for testing, or to bin/publish for distribution.
Bundling extra content (families, resources) into the add-in output.

Workflow

Step 1: Deploy or publish

<DeployAddin>true</DeployAddin> <!-- to %AppData%\Autodesk\Revit\Addins\<version> -->
<PublishAddin>true</PublishAddin> <!-- to bin\publish for distribution -->

DeployAddin implies publishing. Override the targets with AddinDeployDir / AddinPublishDir.

Step 2: Include extra content

<Content Include="Families\**" PublishDirectory="Families" CopyToPublishDirectory="PreserveNewest"/>

Step 3: Rely on manifest patching

The SDK removes the ManifestSettings node for Revit versions older than 2027 during publish to support legacy Revit versions.

Step 4: Verify

Build, and confirm the add-in and manifest land in the deploy or publish folder and that Revit loads the add-in.

Validation

Deploy/publish is enabled only in the project holding the .addin manifest.
Extra content is declared with PublishDirectory / CopyToPublishDirectory.
The manifest works across supported years via SDK patching.

Common Pitfalls

Pitfall	Correct approach
Enabling deploy in a class-library project with no `.addin`	Enable it only in the manifest-owning project.
Copying families with a raw `<None>` item	Use `<Content … PublishDirectory=… CopyToPublishDirectory=…/>`.
Hand-editing the manifest per Revit version	Let the SDK patch `ManifestSettings` on publish.