Description
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.
Key Learnings
- 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
Speakers_few
- SCScott ConoverScott 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.
Jeremy TammikJeremy is The Building Coder. He works with the Forge Partner Development team on Autodesk APIs and web services, providing developer support, training, conferences, presentations, and blogging on the Revit API and cloud and mobile technologies. Jeremy is a prolific author and passionate about cooperation and sharing. Jeremy graduated with degrees in mathematics and physics, worked as a teacher and translator of both computer and human languages and as a C++ programmer on early GUI and multitasking projects. Jeremy is fluent in six European languages, vegetarian, has four kids, three grandchildren, loves cooking, climbing, hiking, sports, nature, literature, adventure, survival, problem solving and challenges of all kinds.
Sasha CrottySasha Crotty leads Autodesk’s AEC Platform Data team, focused on building an open and extensible data platform connecting AECO teams in their tools of choice. Since joining Autodesk in 2005 has taken on multiple roles from writing code for Revit Structure to product management for the Revit platform and services. 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.