RevitAddInManager does not work with nice3point MultiProjectSolution template when using DI at application startup

[kjs-chang]

Description

I tested running and debugging an add-in created from the nice3point MultiProjectSolution template using RevitAddInManager.

However, an error occurs when executing the command through RevitAddInManager. From my investigation, the issue appears to be related to the dependency injection (DI) initialization that normally happens during the Revit application startup phase.

My assumption is that RevitAddInManager directly invokes the command implementation, bypassing the add-in startup sequence where the DI container is configured and services are registered. As a result, dependencies cannot be resolved correctly when the command is executed through AddInManager.

Expected Behavior

The command should be executable through RevitAddInManager in the same way as when the add-in is loaded normally by Revit.

Actual Behavior

An exception occurs because required services are not initialized or cannot be resolved from the DI container.

Question

Is there a recommended way to use RevitAddInManager together with the nice3point MultiProjectSolution template and its DI-based startup architecture?

Has anyone encountered a similar issue, and is there a known workaround or best practice for testing/debugging commands in this scenario?

I'm not sure whether this is an inherent limitation of RevitAddInManager's execution model or if there is additional configuration required on my side. Any guidance would be appreciated.

[chuongmep]

Hi @kjs-chang , can you share the link details to reproduce the issues, how to reproduce the issue you are facing ?
@Nice3point , is that because you design to load from ribbon or interface in external command ?

[kjs-chang]

@chuongmep Do you mean that changes can still be applied even when the DLL is already loaded and being used by the Revit process?
I am using Visual Studio 2026, so I believe all the required features should be available. However, regardless of the method I try—including debugging or attaching to the process—Hot Reload is not available in my environment.

I'm currently running the application using Run (F5) in Visual Studio.
As shown in the image, the Hot Reload indicator displays a prohibited (🚫) icon, and changes to Margin or Font properties in XAML are not being applied to the running application. The same issue occurs with Live Preview.
I have already verified that Hot Reload is enabled in the Visual Studio settings.
Are there any other settings or requirements that I might be missing?

[Nice3point]

@kjs-chang check if IsRepackable enabled in .csproj. If yes, then hot reload will be broken gluck/il-repack#386.

Disable Il repack to enable hot reload (it can cause DLL conficts. be careful) or use Revit 2027 with a builtin Addin isolation for debugging

[kjs-chang]

@Nice3point Can hot reload be verified using the MultiProjectSolution sample as well?
Why isn't it working in my case?
Tests are being conducted with Revit 2025, 2026, and 2027.

<DeployAddin>true</DeployAddin>
<LaunchRevit>true</LaunchRevit>
<EnableDynamicLoading>true</EnableDynamicLoading>
<IsRepackable>false</IsRepackable>

[Nice3point]

@kjs-chang questions about VS not for me, im a JetBrains boy. With false hot reload should works