Enterprise CUI and other AutoCAD Verticals

[GreyHippo]

I have some users running Civil 3D and some running plain AutoCAD. I have a enterprise CUI with some partials loaded (c3d.cui, map.cui, etc.) Do I need to have a separate enterprise CUI for plain AutoCAD users so that C3D commands do not get loaded?

[BlackBox]

I have some users running Civil 3D and some running plain AutoCAD. I have a enterprise CUI with some partials loaded (c3d.cui, map.cui, etc.) Do I need to have a separate enterprise CUI for plain AutoCAD users so that C3D commands do not get loaded?

Why not leave the native CUIx files mapped to Main CUI as-is OOTB for each installation, and add only your internal customizations to your Enterprise CUI(s)?

If you have internal custom CUI elements that can only run in verticals, then be sure to make a separate CUIx for each vertical installation, and leave those elements that function properly in both vanilla AutoCAD, and verticals in a separate CUIx. Then simply setup a per-installation Enterprise CUIx (empty), which maps as partial only AutoCAD CUIx for vanilla AutoCAD installs, and your AutoCAD CUix + your Civil 3D CUIx (as example) for Civil 3D installs. Less duplication, and much simpler to maintain.



As an aside, some vertical CUIx files contain duplicate Commands, etc. as ACAD CUIx, and some elements have been reported to exhibit misbehavior when not part of Main CUI (as is the case OOTB). Further, you're not enabling C3D or Map functionality for those with only vanilla AutoCAD, as none of the prerequisite framework, assemblies, etc. exist, so you're simply introducing unusable (duplicate?) CUI elements when you map all OOTB CUIx into your Enterprise CUI.

HTH