Nice3point.Revit.Templates 5.0.0

Prefix Reserved 
dotnet new install Nice3point.Revit.Templates::5.0.0
This package contains a .NET Template Package you can call from the shell/command line.

Create your Add-In for Revit on the .Net platform

Nuget Downloads Last Commit

This repository contains a project templates for creating Revit Add-In.

Template Features

  • Revit multi-version support.
  • Publishing GitHub releases.
  • Creating a multi-version installers.
  • MVVM pattern with Modal and Modeless windows.
  • Creating a bundle for publishing to the Autodesk Store.
  • Application and Command add-in types.
  • GitHub Actions and Azure DevOps pipelines.
  • Dependency Injection.
  • Add-in logging.

Installation

  1. Install the latest .Net SDK.
  2. Run dotnet new install Nice3point.Revit.Templates to install the project templates.

Usage

  • To create a project use the IDE or run dotnet new.
  • For more information, read Wiki.

  • net9.0

    • No dependencies.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
5.0.0 474 4/2/2025
4.0.7 1,451 8/25/2024
4.0.6 266 7/22/2024
4.0.5 288 6/23/2024
4.0.4 546 5/21/2024
4.0.3 390 4/14/2024
4.0.2 232 4/8/2024
4.0.1 233 4/2/2024
3.2.2 1,905 1/11/2024
3.2.1 236 1/11/2024
3.2.0 404 1/4/2024
3.1.1 863 6/7/2023
3.0.1 401 4/9/2023
2.4.2 907 10/14/2022
2.3.0 442 7/31/2022
2.2.0 524 6/29/2022
2.1.0 459 6/14/2022
2.0.0 627 4/5/2022
1.7.3 534 1/2/2022
1.6.0 1,522 11/26/2021
1.5.0 335 11/16/2021
1.4.1 375 11/10/2021
1.3.3 338 11/7/2021
1.2.0 380 10/7/2021
1.1.2 372 10/4/2021
1.0.1 415 9/6/2021
1.0.0 533 9/5/2021

Solution template

• The release publishing pipeline has been completely redesigned. Publishing is now based on tags instead of automatic push to main branch. This is aimed at better control to avoid unexpected situations. Also improved pre-release publishing, and releases from any branch, e.g. it is now possible to release an Alpha version from the develop branch. See [Wiki](https://github.com/Nice3point/RevitTemplates/wiki/Publishing-the-Release) for more details.
• The installer now ignores all .pdb files.
• Improved Readme file, added all detailed documentation about building and publishing the project. Readme file is dynamic and depends on the settings specified when creating Solution.
• Code coverage with documentation.
• Reworked .yml files.
• Simplified some code.
• Added support for .NET 9.
• Added support for Revit 2026.
• Removed support for Revit 2020. For support, add it manually by [guide](https://github.com/Nice3point/RevitTemplates/wiki/Managing-API-compatibility).

Solution migration from v4 to v5

1. Create a completely clean project with the same name based on v5 of the template.
2. Copy the following folders and files to your working project with replacement:
  • build folder.
  • install folder.
  • Readme.md file.
  • .yml files.
3. Review the Git Diff carefully:
  • Keep your custom GUIDs and project names.
  • Preserve any user-specific customizations.
  • Roll back any changes to your business logic.
4. Update your solution's dependencies to match v5 requirements.
5. Test the build process to ensure everything compiles correctly.

Add-in templates

• Enabled Nullable by default.
• Added IsRepackable property, disabled by default. [Read more](https://github.com/Nice3point/RevitTemplates/wiki/Publishing-the-Release#dependency-conflicts).
• Added ManifestSettings section to manifest for enabling dependency isolation, starting with Revit 2026 API.
• Added more WPF converters.
• Fixed typos.
• Updated dependencies.
• Added support for Revit 2026.
• Removed support for Revit 2020.

Add-in migration from v4 to v5

1. Update your .csproj file:
  <!-• Replace this line -->
  <PublishAddinFiles>true</PublishAddinFiles>
  
  <!-• With these lines -->
  <DeployRevitAddin>true</DeployRevitAddin>
  <EnableDynamicLoading>true</EnableDynamicLoading>

2. Update your .addin file by adding the ManifestSettings to enable add-in isolation in the Revit 2026:
  <RevitAddIns>
    <!-• ... existing settings ... -->
     <ManifestSettings>
         <UseRevitContext>False</UseRevitContext>
         <ContextName>RevitAddIn</ContextName>
     </ManifestSettings>
  </RevitAddIns>

3. Review and update any nullable reference types in your code as they are now enabled by default.