A couple of quick topics to start the week:
Add-In DLL Signature
As I mentioned migrating RvtSamples to Revit 2017, the 'Security – Unsigned Add-In' message is now displayed by Revit when an unsigned add-in DLL is detected.
We raised that question briefly in the Revit API discussion forum thread on code signing of Revit addins, and the issue came up again in another case yesterday:
Question: I signed my add-in, expecting that doing so would suppress the 'Security-Unsigned Add-in' message displayed during Revit start-up:
However, even when this DLL is signed, a similar dialogue appears, requiring user input:
Can this dialogue be suppressed?
I would prefer it not to interrupt the user experience during Revit start-up.
Answer: Please study the new section on Digitally Signing Your Revit Add-in in the Online Revit 2017 Help > Developers > Revit API Developers Guide > Introduction > Add-In Integration > Digitally Signing Your Revit Add-in.
It was updated just now and will hopefully resolve all your questions.
BIM 2 in the UK
The UK Mandates BIM Level 2.
In May 2011, it was announced that all UK government construction projects would be required to adhere to BIM Level 2 by 2016.
That time is now.
The Autodesk BIM 360 web site offers a whitepaper explaining more.
Have fun with it, and congratulations to the UK BIM community for agreeing on such an important undertaking!
Communication between AutoCAD and Revit
I am developing an application that will use both AutoCAD and Revit.
I develop a design in AutoCAD and then open that design data in Revit.
What is the best method to achieve this?
I see a couple of feasible options:
- Direct link between AutoCAD and Revit in a class inheriting from
IExternalCommandand passing data directly through method calls.
- Using an external third executable program to act as an intermediary.
- Using a file as an intermediary.
- Implementing a TCP connection between programs.
Are there any other options?
Answer: I would suggest trying number 1 first.
There are two important aspects to consider here.
First, AutoCAD makes it really easy for you, since it provides a COM interface that can be driven through .NET and can be used to access the AutoCAD.NET API from outside AutoCAD.
For instance, through it, you can launch AutoCAD, open, create, read, write and otherwise manipulate a drawing, and close down AutoCAD again.
Secondly, you cannot do the same for Revit.
Revit makes it a little bit harder for you to drive it from outside.
The Revit API is entirely based on events.
You cannot use the Revit API except in a valid Revit API context, and a valid Revit API context is provided by Revit API events and nothing else.
For more details on this, please refer to The Building Coder topic group on Idling and external events for modeless access and driving Revit from outside.
Now for the good part: the combination of these two is easily possible.
You can implement a Revit add-in that also makes use of the AutoCAD.NET API and thus achieve the direct link that you suggest in item 1.