Debug Revit 2025 pluggin on visual studio 2025.

Debug Revit 2025 pluggin on visual studio 2025.

pmeigneux
Advocate Advocate
1,693 Views
4 Replies
Message 1 of 5

Debug Revit 2025 pluggin on visual studio 2025.

pmeigneux
Advocate
Advocate

hi,

It is no longer possible to give the name of an executable to debug a Revit plugin. Do you have a solution ?

 

pmeigneux_0-1715711642305.png

Philippe.

 

Accepted solutions (1)
1,694 Views
4 Replies
Replies (4)
Message 2 of 5

pmeigneux
Advocate
Advocate

Sorry, visual studio 2022..

0 Likes
Message 3 of 5

Moustafa_K
Collaborator
Collaborator

yep, you need to do it manually. When you create this Debug Profile you will see a new file created named "launchSettings,json" under Properties folder in the solution explorer. compare what you have with this one below, or even you can replace it all with the correct folder path to the Revit.exe file

 

 

{
    "profiles": {
        "Revit2025": {
            "commandName": "Executable",
            "executablePath": "C:\\Program Files\\Autodesk\\Revit 2025\\Revit.exe",
            "commandLineArgs": "/language ENU"
        } 
    }
}

 

 

 see if this helps

Moustafa Khalil
Cropped-Sharp-Bim-500x125-Autodesk-1
Message 4 of 5

nice3point
Advocate
Advocate
Accepted solution

Paste it in the .csproj file

<PropertyGroup>
    <StartAction>Program</StartAction>
    <StartProgram>C:\Program Files\Autodesk\Revit 2025\Revit.exe</StartProgram>
    <StartArguments>/language ENG</StartArguments>
</PropertyGroup>

 

Message 5 of 5

farid.nacer
Explorer
Explorer

For anyone else running into this, the simpler solution is to delete the profile (Impararia.RevitImport in the screenshot) and create a new profile of type Executable (instead of Project). No need to mess with the config files.

0 Likes