Autodesk addins6/6/2023 ![]() ![]() Here we print another message to the console.“ if $(Configuration) = 2017 goto 2017” basically means that if I select Configuration named “2017” please jump over to piece of code that starts with “ :2017“.In this case the selected Configuration name. “ echo” is used here to print something to the console.Let’s break that down a little bit first: Now, how can we connect our Post-Build Events with our Configurations settings so that we can build these tools for different version on a fly? Here’s an example of conditional statements embedded into Post-Builds so that we can quickly change between versions: That usually saves me a few seconds every time I want to launch Revit to see my new tool in action. I start off my every Revit plug-in project by creating a Post-Build Event that copies my freshly minted DLL to Autodesk/Addins folder. How can we go about maintaining code for multiple versions of Revit, and easily building it for any version at any time. What about that one user in the office who still works on a project from 5 years ago, and refuses to update to latest Revit 2018? Do I have to maintain a version of my plug-in for that guy too? The answer is probably yes. ![]() Yes, we all love shiny new toys, but they usually break our old reliable tools. One thing that we all have a love/hate relationship with is API breaking changes.
0 Comments
Leave a Reply. |