Updated the version number to 2015.0.109.0.Īs expected, an error is generated in the CmdSheetSize.cs module:.
Update the RevitAPI.dll and RevitAPIUI.dll references.We should be pretty well set for the migration, having alreadyįuture proofed The Building Coder samples.Īll I have to do is perform the same steps I already described for the That was it, and here is the ribbon panel containing the RvtSamples top level menu: In RvtSamples.txt, I replaced the default Revit SDK installation location by my personal installation folder, i.e. It reads a text file defining the path and external command implementation name of each of the samples and sets up one big menu of them all for you.Īs always, I added the add-in manifest RvtSamples.addin and the input text file RvtSamples.txt to the RvtSamples project files to make them easier to open and manipulate. You can save yourself the effort by installing one single external application instead, RvtSamples.
It would be rather laborious to install a separate add-in manifest for each of the over hundred external commands defined by the Revit SDK samples. If you want to run and test any of the SDK samples, you again have a choice between the laborious approach and the automated one. I thus executed the following commands to discover the required assembly reference paths and ensure that they are found where expected:Ĭd C:\Program Files\Autodesk\Revit Architecture 2015Ĭp RevitAddInUtility.dll RevitAPI.dll RevitAPIIFC.dll That is what I did this time around, after checking the current values of the HintPath tags using jhint.exe. The Autodesk Building Design Suite Ultimate 2013. Yet another option, and possibly the most elegant of all, is to simply copy the Revit API assemblies into the expected locations and avoid modifying any project files at all, as I explained when Process the Revit 2009 SDK project files. I implemented jhint back in the year 2008, to by my jhint utility, or using the RevitAPIDllsPathUpdater.exe utility provided in the Revit SDK. This can also be done for you fully programmatically, e.g. using search and replace functionality to modify the HintPath tag value. The most stupid approach would be to go and manually edit each and every one of the over hundred Revit SDK project files using the Visual Studio IDE.Ī less stupid approach would be to edit all the project files globally in an editor, e.g. I currently only have Revit Architecture 2015 installed, and the SDK apparently assumes by default that you have Revit One-box installed, so I needed to update all the Revit API references – or find another solution to ensure they are found. Go take a look in one of them with a text editor, e.g. The latter is defined by the HintPath tag in the project files. There is one small issue to deal with first, though: where are your Revit API assemblies located, and where do the Visual Studio project files expect them to be? The Revit SDK includes a master Visual Studio solution file SDKSamples2015.sln, so you basically just have to open that in Visual Studio 2012 and say 'build all'. Compiling the Revit 2015 SDKīefore migrating The Building Coder samples, I downloaded and compiled the updated Revit 2015 SDK from the Download, Compile and Install RevitLookupĪll you need to do for RevitLookup is clone theĬompile and install as usual. You can bet I did some of it differently last time around.īy the way, the good news is that it is much simpler this time, and getting simpler every release.
The new API functionality is available, and I migrated The Building Coder samples to Revit 2015.Īfter doing so, I went out and spent a few hours on a hill enjoying the full moon – enjoying nature, some time, some space for myself – ca. RevitLookup for Revit 2015 is available on GitHub, Released last week, the Revit SDK was posted and updated,