![revit 2011 update revit 2011 update](https://i.pinimg.com/originals/70/52/75/705275d7cd964c658738e43dc5e59405.jpg)
With manual regeneration, you issue a Document.Regenerate any time that you want the project to regenerate.
#REVIT 2011 UPDATE CODE#
However, if you had been using transactions within your code in the past (i.e. Manual – the developer must control their own transactions explicitly.įor upgrading an existing application, you’ll probably want to stay with Automatic because it most closely matches the prior release behavior.Automatic – like what has existed historically.Commands are now attributed with one of two Transaction modes: There are fundamentally new transaction mechanisms that you will likely need to deal with (unless your application was very straightforward). See our separate post on the new mechanism (which is quite superior) – but it may take a minute or two to re-work any of your code which iterates through elements in the document (which almost every command does at least once).Īlso note – the View.Elements collection has also been re-worked to the new scheme. The Document.Elements collection, the Document.get_Elements( type ) and the filter mechanism have all been removed. Where Did My ElementIterator Go?Īutodesk has taken somewhat of an unusual step in 2011 – that of ripping and replacing all of the three different element search and iteration schemes from before 2011 and replacing them with the new FilteredElementCollector. These are further described in the “What’s New” section of the API Help FileĪutodesk is also providing in the SDK a spreadsheet of all of the class renames, and their corresponding new names.
![revit 2011 update revit 2011 update](https://3.bp.blogspot.com/-tpC-R1ZrjD0/TrrGO9wbI8I/AAAAAAAAAL0/fmKTf9guTOo/s1600/notingin3d.jpg)
![revit 2011 update revit 2011 update](https://i.ytimg.com/vi/HRgFtcHQb7M/maxresdefault.jpg)
the old Geometry.Instance class has been renamed to GeometryInstance.the old Geometry.Element class has been renamed to GeometryElement.the Symbol class has been re-named to “ElementType”..Structure ( Analytical Model, Loads, Rebar, Trusses, etc)..Plumbing ( Piping, PipingSystems, etc)..Mechanical (Spaces, Zones, SpaceTags, Ductwork, etc)..Events (contains the event arguments for all the different kinds of events)..Electrical (contains electrical-related elements and concepts, from CableTray to DemandFactor)..Architecture ( contains architecture-specific elements like Rooms, RoomTags, Gutter, Fascia, etc).(this is the container for most core elements, geometry, parameters, and other concepts).(where all the User Interface and command/application integration classes landed).While I won’t cover the namespaces in detail here, to give you an idea of what you’re looking at: While I would argues that this is probably a good thing in the long term, it will require a bit of work to recompile your code. The factory has taken this opportunity to completely re-work the namespace hierarchy into something which more closely matches Revit’s internals – as well as to clean house, straighten up, and simplify some things.
![revit 2011 update revit 2011 update](https://a-static.mlcdn.com.br/618x463/autodesk-revit-architecture-2011/umlivro2/4919780470610114/8c7a5e20cf71e30fe43edbf55e28bf56.jpg)
Installer changes (if you want to take advantage of new capabilities).Replacement of the Analytical Model classes.Changes to the Element.ObjectType structure.Non-trivial changes to the fundamental XYZ, UV and ElementId class.Fundamentally new transaction and regeneration mechanisms.Deprecation and replacement of many of the fundamental element search and iteration APIs.Massive namespace renaming/restructuring.While previous upgrades have been fairly painless, in 2011 you’re up against: If there is a dark side to all of the positive changes in the 2011 API – it is that the amount of re-work required for existing add-ins is FAR more than previous upgrades.