Hello Folks;
How can I code without getting “Multiple Definition” Warning and without having to write the full name space everytime? NOTE that I’d like to keep the Packages that cause this conflict such as Open MEP and Orchid. I CANT delete them I need them! any ideas?!
Hey mate, it’s a simple fix. The answer is sort of given to you on the warning itself.
Just need to add the relevant prefix to the code.
Instead of just Point.ByCoordinates(0,0,0), do specify which package it should be referring to. Like Autodesk.DesignScript.Point.ByCoordinates(0,0,0)
thank you my friend for reply, yet, as I mentioned, I would like to code WITHOUT having to write the full name space like “Autodesk.DesignScript…” you know what I mean 
I’m hoping there is a workaround for this issue
Not without removing custom packages. The issue is that you have multiple libraries that use the same class or namespace. In order to specify which one you want to use, you have to use the full namespace.
you could theoretically modify the element resolver inside your .dyn - I have not tried it but it should have a list of aliases for the different types - I’m not sure if we prefer the autodesk types by default though.
This has been a big problem for the Civil 3D (line, curve, and basically everything but points and polycurves) and now also the Revit integration (surface!), even without customizations.
I don’t know that configuring the .dyn will help. Will it fix autocomplete to not get in the way? Currently Surface. will redirect to the Analytical. namespace.
I tested this early on and it seemed to default nicely. Migrating from an old graph worked fine in my testing as well. Is there another situation where it becomes troublesome?
Which build is that?
Are you using a ‘clean’ system with no other Dynamo versions on it?
How many custom packages do you have in the library?
It may be due to me having… 13 different Dynamo Sandbox and and… 8 Dynamo Revit versions… 5 Civil 3D versions… Some FormIt ones… a pair of Robot ones… at least one Alias one…
That was in the latest version of Civil 3D (2025.2). I currently have 7 versions of Civil 3D installed, 1 Revit version, and 1 Sandbox version.
I didn’t have any packages installed in the above recording, but I just downloaded a bunch and tried again. DesignScript.Point was still at the top of the list, but it wasn’t the default selection. That would’ve been nice.
Yeah this is what gets me. It’s first, but it’s not default. If you just type ‘Point.B’ I don’t get DesignScript.Point.B in the code block, I get AutoCAD.Point.B so I have had to teach myself to type ‘Point:arrow_up:
.B’ or ‘Point:no_entry_sign:.B’ or similar… Fortunately even if the design script is written in say Sandbox the name spaces resolve correctly due to the element resolver which maps things well between Dynamo flavors.
Unrelated: how do you function without more sandbox versions? I limited myself to only versions after 2.10 and I feel naked now.
I probably just don’t need them as much as you do 
I really only deal with Dynamo for Civil 3D on a regular basis.
Here’s the behavior I see - if you ‘stop’ after typing you’re good, but if you’re quick and just keep going… yipes!
Also the namespace Point doesn’t auto resolve the way I thought it would, so Escape doesn’t help. Hitting up many times does though.
