BOLT OUT OF THE RED

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...

is not always the correct approach.More...

Before I cover debugging… It looks like the classic UI is still with us. While this is encouraging as a short term solution and not totally surprising, I can’t see it being in Revit 2011 or above. With the API they’ll have to put back the toolbar code. Which means 3rd party developers will have to accommodate both solutions (ribbons, toolbars). Bit of a mess but then again so is the ribbon and I’m sure there will be many happy customers if they give us a choice until the messribbon is fixed.

Debugging in Revit 2010

I noticed from Ed’s post that he’s having problems debugging in 2010.More...

After a considerable amount of work I’ve finally managed to complete what is by far my most significant Revit API command to date. In trying to figure out what would attract AutoCAD users to Revit I hit upon what I consider to be the missing link. This command will also be very useful for Revit experts.More...

As I explained in part 3 if a command fails to run other than in the Revit executable directory, there is a good chance it’s because of the command assembly was loaded into the wrong binding context (LoadFrom() ) by Revit. In this part of the series I’m going to explain how we can fix this so you can place a command in any directory..More...

Compared with the path only option previously available, passing the Button data an ImageSource is a vast improved in the Revit 2010 ribbon implementation. However, manipulating Image objects in .NET3.5 is quite different to Images in .NET2.0. More...

You’ll see from the preview information out there that Revit 2010 requires .NET3.5 . There wasn’t anything stopping you from using .NET3.5 with the Revit API in previous releases, but now it’s official there isn’t any excuses not to use one of the coolest aspects of .NET3* .More...

As I mentioned in part 1 , using the advanced classes in System.Configuration in Revit API commands won’t run out of the box. That’s a bit of a generalisation. With a standard installation of Revit, an API command that is using System.Configuration’s more advanced classes such as ConfigurationSection will only work from one location. The directory of the Revit executable (Revit.exe). On XP32 this is usually C:\Program Files\Revit Architecture 2009\Program . More...

Out of interest I took the same code I used in this post and with the required changes for using in VSTA, ran the macro against the same project in the previous post.More...