Here are some notes on the small issues I encountered compiling the Revit 2014 SDK:
- Compile and install RevitLookup
- Set up the Revit API assembly paths
- First compilation run causes expected errors
- Set up the RevitAddInUtility assembly path
- PointCurveCreation Office reference
- CancelSave RevitAddInUtility Reference
- Set up the RvtSamples application
- Fix errors in RvtSamples.txt
- Download RvtSamples and RevitLookup
I already described this same process during the Revit 2013 timeframe. Let's see if anything changed, or, better still, improved.
Compile and Install RevitLookup
My first step is always to compile, install and test RevitLookup.
This went completely smoothly, so I have nothing to report on that.
Please see below for a link to the version I compiled.
Set up the Revit API Assembly Paths
Before the introduction of Revit Onebox, I used to make copies of the Revit API assemblies for the different flavours.
With the advent of Onebox, I opted for the simpler solution of using the Revit API DLLs path updater RevitAPIDllsPathUpdater.exe. Simply launch it, enter the sample location and DLL folder, and let it do its job. In my case, I entered the following paths:
- Sample location: C:\a\lib\revit\2014\SDK\Samples
- DLL folder: C:\Program Files\Autodesk\Revit Architecture 2014
It completes and reports that it "Replaced 169 files, skipped 0 files."
First Compilation Run Causes Expected Errors
With the correct assembly paths in place, it is time to open the Visual Studio solution SDKSamples2014.sln and compile the samples.
The first run reports Rebuild All: 166 succeeded, 3 failed, 0 skipped.
This no surprise, because there are some expected errors.
Set up the RevitAddInUtility Assembly Path
The first error is caused by the RevitAddInUtilitySample and says: "The type or namespace name 'Autodesk' could not be found (are you missing a using directive or an assembly reference?)"
The RevitAddInUtilitySample references the RevitAddInUtility assembly. It is also located in the Revit API assembly path, but RevitAPIDllsPathUpdater.exe does not take it into account, so you have to open that project and set the assembly path manually instead:
In my case, the correct reference path to it is C:\Program Files\Autodesk\Revit Architecture 2014\RevitAddInUtility.dll.
PointCurveCreation Office Reference
The Massing PointCurveCreation sample references Microsoft.Office.Interop.Excel in order to interact with spreadsheets.
I have not set up Office on my virtual machine, so that caused an error saying "The type or namespace name 'Office' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)"
For a quick ad hoc solution to this, I simply unloaded this one project for the time being.
CancelSave RevitAddInUtility Reference
The next problem occurs in the Events CancelSave sample: "The type or namespace name 'RevitAddIns' does not exist in the namespace 'Autodesk' (are you missing an assembly reference?)"
Same resolution as above, set the RevitAddInUtility assembly path.
That was it!
No more errors, just 345 warnings saying 'There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "RevitAPI, Version=2014.0.0.0, Culture=neutral, processorArchitecture=AMD64", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project'.
I assume you can ignore those.
This was a smoother compilation than ever before.
Set up the RvtSamples Application
I always install RvtSamples to load all the other SDK samples if I ever want to test something in one of them.
It saves you from installing them one by one, which might prove a lengthy process, there being well over a hundred of them.
To do so, I first add two files to the RvtSamples project, its add-in manifest and its text file listing all the samples to load:
In the text file, I replace the samples path by my real installation folder, globally replacing "Z:\SDK2013\Samples\" by "C:\a\lib\revit\2014\SDK\Samples\".
At the end, I add placeholders for my two include files, for the Autodesk Developer Network ADN and The Building Coder sample collections:
##include C:\a\lib\revit\2014\adn\src\AdnSamples.txt #include C:\a\lib\revit\2014\bc\BcSamples.txt
The ADN samples are commented out, because we have not completed their migration yet.
I already migrated The Building Coder samples to Revit 2014, though, so that include file is already active.
I need to add the RvtSamples assembly path to its add-in manifest and install that in the Revit Add-Ins folder, and we are set to go.
Fix errors in RvtSamples.txt
As usual, the list of samples to load specified by RvtSamples.txt is not perfectly set up. Here are some of the add-ins causing errors on my system:
- ProjectUnit (missing)
- PointCurveCreation (my fault)
- BarDescriptions (missing)
ProjectUnit is missing, presumably because the unit API changed in Revit 2014 and the sample has been removed. It is still listed in RvtSamples.txt, and should be removed there as well.
Most of the others are caused by VB.NET samples listed in their 'bin' subfolder, whereas their assembly DLL really lives in 'bin/Debug', at least on my system, and vice versa, in the case of CreateShared.
After my first clean-up pass, the following still cause problems:
- PointCurveCreation (my fault)
- BarDescriptions (missing)
Again, these are almost all VB.NET samples. Something strange going on with those.
There is a testing switch you can set in the RvtSamples source code, actually:
bool testClassName = true;
Setting it to true turns up more errors:
I fixed some of these, but not all.
Anyway, I'll stop fixing this for today, though, because I have other things to do as well.
RvtSamples loads now and most of the samples are available:
Download RvtSamples and RevitLookup
Here is my current version of RvtSamples, and also of RevitLookup, which was missing from some intermediate versions of the SDK samples.
The RvtSamples package includes both the original and my modified add-in manifest and RvtSamples.txt sample list. You can compere them to see the changes I applied, and add analogous changes of your own for any other samples that you wish to activate.
I hope this is of use to you.
This article was picked for TenLinks Daily by www.caddigest.com.
Actually, taking a closer look at the CAD digest listing, I currently count 53 of The Building Coder articles listed there. I was not aware of that before. Surprise, surprise :-)