Error uri resource when Click button in Revit

Error uri resource when Click button in Revit

manhgt214
Enthusiast Enthusiast
479 Views
4 Replies
Message 1 of 5

Error uri resource when Click button in Revit

manhgt214
Enthusiast
Enthusiast

Hello Everyone!

 

I dont know why my revit project when click button is show error in below.
・I tested by Add-In Manager run dll file -> work fine
・I try close Revit then Restart then -> work fine.
Thank Advance!
manhgt214_0-1745544204736.png

 

0 Likes
Accepted solutions (1)
480 Views
4 Replies
Replies (4)
Message 2 of 5

jeremy_tammik
Alumni
Alumni

Sorry, cannot suggest anything. It is impossible to diagnose based on the limited information provided.

   

Jeremy Tammik Developer Advocacy and Support + The Building Coder + Autodesk Developer Network + ADN Open
Message 3 of 5

manhgt214
Enthusiast
Enthusiast

Thank you! I try find solution and reply soon

0 Likes
Message 4 of 5

manhgt214
Enthusiast
Enthusiast
Accepted solution

Sorry I tried find solution and below is new information:

I realize after run .dll file same with .dll file built to add-in by add-in manager then after click a button will show that error
But only class created by Wpf, class not contain wpf or form created by windows form not error

manhgt214_0-1750667127783.png


I using add-in manager to run it because I want debug it.

Maybe when run by add-in manager file assembly then click to button make by it => not correct.
this is folder add-in manager auto copy dll file and excuted assembly

manhgt214_1-1750667198726.png

this is my addin folder

manhgt214_2-1750667326415.png


...and error

manhgt214_3-1750667484135.png

 

 






  

0 Likes
Message 5 of 5

plDev2024
Community Visitor
Community Visitor

I had exactly the same issue. When loading the testing program via Addin-Manager, all WPF programs on the Revit ribbon stop working and require a Revit restart.

It seems that use Addin-Manager to load a .dll that has already been added to the Revit UI causes confusion—maybe the newer version overwrites the existing one.

Only WPF programs are affected; WinForms and non-UI programs continue to work.


My workaround is to rename the .dll when loading via Addin-Manager by adding a suffix such as "_test".