Jeremy graduated in mathematics and physics in Germany, worked as a teacher and translator, then as a C++ programmer on early GUI and multitasking projects. He left Autodesk in 1994 to work as an HVAC application developer, and then rejoined the company in 2005. He was a co-founder of ADGE, the AutoCAD Developer Group Europe, and a prolific author on AutoCAD application development. He joined Autodesk in 1988 as the technology evangelist responsible for European developer support to lecture, consult, and support AutoCAD application developers in Europe, the U.S., Australia, and Africa. Martin has two drum sets which get to use during ‘down time’, and enjoys travelling and reading.Ībout the Presenters Jeremy Tammik Principal Developer Consultant Developer Technical Services EMEA, Autodesk SARL Jeremy is a member of the AEC workgroup of the Autodesk Developer Network ADN team, providing developer support, training, conference presentations, and blogging on the Revit API. Martin has a beautiful wife and two daughters, and works from his home in San Antonio, TX. Martin is a published co-author of books on AutoCAD MEP and Revit MEP. Martin has a master’s degree in Architectural Engineering from Kansas State University and a master’s in Business Management of Technology from the University of Texas in San Antonio, and is a member of ASHRAE.
Prior to involvement with the development of MEP products, Martin worked in a variety of roles in a number of architecture and engineering firms, including electrical designer, engineering coordinator, and application developer. He has written and presented material on AutoCAD MEP and Revit MEP to coworkers as well as at Autodesk University. In addition, he works with sales and key accounts to help with workflow adoption and to identify technical trends. In his current role as Industry Success Manager, Martin works with product management, product design, and quality assurance teams providing subject matter expertise. Industry Success Manager Autodesk Martin has worked on-site with customers to implement best practices using AutoCAD MEP and Revit MEP, ranging from engineering firms and manufacturers to 3rd party developers. NET The basics of the generic Revit API Revit product and Revit MEP usageĪbout the Presenters Martin J. We do not discuss and assume knowledge of Your current areas of interest and hottest problems Your ideas and visions Your experience Wish list items Programming for MEP in a BIM The functionality of the Revit MEP API The Revit MEP API samples Share and discuss best practices of Revit MEP programming
Objectives of this RME API Unconference What’s New in the Revit 2011 API: New Deployment M.Image courtesy of Hobart, Yañez, Ramos, Maguey, and MartínezĪll Systems Go in Autodesk Revit MEP Programming Martin Schmid.Revit API 2011: User Interface Changes/Improvements.Revit API 2011: Upgrading Existing Add-Ins.Revit API 2011: The New Way to Find Elements.Provide you information about which versions of Revit 2011 are installed (no much reverse engineering 6+ uninstall registry keys!).Īll in all, there are a variety of new features, capabilities and tools which bring more power and professionalism to Revit AddIn deployment in 2011.While it’s no picnic in 2011, beyond the new file format, Autodesk has also provided an all-new redistributable DLL – specifically to help developers do installations in. More Deployment Help Still… For Installers.Īs mentioned above – writing installers for Revit in the olden-days was no picnic. I’ll write more about some of the capabilities implied here – but as you can see it represents a big step forward versus the REVIT.INI file (which still works). NET programmers, I would recommend using the Environment.GetFolder() method, where you can specify:
Windows Vista/Windows 7: C:\Users\\AppData\Roaming\Autodesk\Revit\Addins\2011\įor.Windows XP: C:\Documents and Settings\\Application Data\Autodesk\Revit\Addins\2011\.Windows Vista/Windows 7: C:\ProgramData\Autodesk\Revit\Addins\2011\.Windows XP: C:\Documents and Settings\All Users\Application Data\Autodesk\Revit\Addins\2011\.These new files (typically one for each program) also address some of the issues with permissions – particularly in Vista and Windows 7: And developing installers which would programmatically add and remove things? Ugh!Īutodesk has heard and finally answered the call on this issue – new in 2011 are XML-based “add-in” files. Deploying commands and applications in Revit up until now has required a mental visit back to the 90’s… You had to create or edit sections within the Revit.INI file – keywords and values (and ugly ones at that).