Thanks for the kind words, Anton! That is nice to hear from someone more knowledgable/experienced.
Yes, I thought about this a lot as well. I decided to create custom objects (all under the Camber namespace) for those where the core Autodesk.Civil.DynamoNodes or Autodesk.AutoCAD.DynamoNodes objects do not already exist. I’m assuming that eventually more core objects will be implemented by the Civil 3D team, but I don’t know the timeframe on that. I decided that when those additional classes are added, then I can phase out those parts of the package so there isn’t confusion.
The downside to this is that there is some duplication with the Civil 3D Toolkit, such as Profile Views. I created new Profile View objects under the Camber namespace for two reasons:
(1) I didn’t want to create a dependency with the Civil 3D Toolkit, such that certain parts of Camber would only work if you have the Toolkit also installed. In reality most users will probably have the Toolkit also installed, but I didn’t want to make that assumption.
(2) I shouldn’t be creating any classes within the Autodesk namespace. That would not be a best practice.
I appreciate that you noticed! As you know, it is a lot of work 