Are you an Revit-based software developer who has run into issues supporting your add-ins in a workshared environment? Have you hit situations where elements can't be edited or updated due to conflicts? As a followup discussion to DV1888: Facing the Elephant in the Room: Making Revit® Add-ins That Cooperate with Worksharing, join this roundtable session to further discuss the techniques that are available to developers to operate on workshared models. Bring questions from your own development experience or more detailed questions inspired by the lecture and discuss the possibilities with a group of experienced Revit API developers. Knowledge of C# and Revit API is required, and prior experience with Revit worksharing will be helpful.
- Explain the basics of Revit worksharing techniques and terminology, especially features that affect add-in development
- Design a Revit add-in to work well in a workshared environment
- Determine the right way to open, read, and/or modify a workshared document for your purposes
- Describe how to deal with both file-based worksharing and server-based worksharing from your add-in
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. 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 United States, Australia, and Africa. He was a co-founder of ADGE, the AutoCAD Developer Group Europe, and a prolific author on AutoCAD application development. He left Autodesk in 1994 to work as an HVAC application developer, and then rejoined the company in 2005. 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 is fluent in six European languages, vegetarian, has four kids, plays the flute, likes reading, travelling, theatre improvisation, carpentry, and loves mountains, oceans, sports, and especially climbing.
Scott is a Software Development Manager in the Revit® development team, focused on API and Interoperability. Since joining Autodesk in 2007, he has led a team working on the design, implementation and testing of the rapid expansion of the Revit® API.Scott has 15 years of experience producing Application Programming Interfaces for parametric 3D modeling systems in a variety of languages and styles. His primary focus has been to enable customers to automate repetitive tasks, extend the application user interface, and transfer data between the application and different data formats. Scott holds a Master of Computer Systems Engineering degree from Northeastern University with a concentration on CAD/CAM/CAE.
Sasha Crotty joined Autodesk, Inc., in 2005 as a developer for Revit Structure software. She went on to lead the Revit Structure Development Team before switching gears into product management. As the Revit Platform Services product manager, she is responsible for the direction and evolution of Revit's multi-disciplinary tools, Collaboration for Revit, performance, and the Revit API. Sasha holds a BA in Architecture and a BS in Electrical Engineering and Computer Science from the University of California, Berkeley, as well as an MBA from Boston University. In her spare time Sasha enjoys growing miniature orchids and traveling around the world.