For those of you excited by .NET4.0’s new features and wanting to test Revit commands compiled with .NET4.0, you’re in luck. Before I show you how, a few caveats:More...

Jeremy nicely summed up the issues with the RevitAddUtility.dll . I thought I’d document my solution which uses interfaces to solve the issue. The problem is the loader exception fires before your application can catch it. By using interfaces you can utilise the appropriate assemblies which maintaining a single main application and no file copying.More...

Steve’s post on IFC and the comments that follow, mirror discussions I’ve had on IFC on numerous occasions. I’m going to be more blunt than Steve though ;-) . Don’t get me wrong, an open interoperability layer is vital for BIM but IFC is not the long term solution.  More...

I’ve had some requests for compiled assemblies of the Autodesk Revit 2011 API SDK samples. They’re useful for those of you who don’t have Visual Studio installed or don’t know how to compile them.  Or if you’re wondering what’s supplied in the SDK and just what’s possible with the API.More...

To be honest I’m loathed to single out a single standout feature from the new API’s. There is no doubt Updaters are going to be widely use. They plug a major gap in the API’s capabilities, the Updater API is well designed and are fast. However, there is a single API that does standout and in my opinion allows developers to begin the process of seamlessly integrating Revit into users BIM workflows unlike anything that has been possible before.More...

API performance has always been of interest, even more so as large projects regularly hit >300Mb now. With the new API’s such as updaters and the DocumentChanged event performance testing has got a lot more complicated. Throw in transaction and regeneration issues and it soon became obvious a different approach was required. I’m not ready to talk about this approach but I thought a little test on transactions speaks volumes about some of the additional design decisions API authors need now consider.More...

As Jeremy noted Revit 2011 API has had a major refactoring of the namespaces as well as splitting into 2 assemblies.More...

So apparently we can talk about Revit 2011 now and wow, can we talk about Revit 2011 and the API…More...

As anyone who tried the Christmas ribbon solution would have found, it lacked one feature. The ability to handle context switching between standard projects and familiesMore...

It’s that time of the year, so why not finish with a post on what has probably been the most controversial aspect of the Revit 2010 release, the ribbon. More...