NXOpen .NET API Reference — Namespace Overview

This is the API reference for NXOpen when used from C# or VB.NET. Class and member names are identical across both languages (it's the same CLR assembly); only syntax differs — see the NX Open Programmer's Guide and the "Getting Started" guides for language-specific sample code style (C# uses NXOpen.Session session = ...;, VB.NET uses Dim session As NXOpen.Session = ...). The reference guide content itself does not show side-by-side C#/VB.NET code samples on the namespace/class summary pages — those live in the Programmer's Guide and per-topic samples, not this alphabetical reference.

Navigation technique (differs from the Java reference guide)

Unlike the Java reference guide (a raw Javadoc frameset), this book uses a Doxygen-generated frameset. It still matches the "no id/name on content iframe" pattern — document.querySelectorAll('iframe')[0] is the content frame — but the internal navigation differs:

• There's a left/top accordion with "Main Page / Namespaces / Classes" entries; clicking "Namespaces" → "Namespace List" loads .../nxopen_net/namespaces.html in the content iframe, which is a single flat, collapsible tree of every namespace (▼/► indicate expandable nodes with sub-namespaces).
• Fastest technique: once the wrapper page has set its signing cookie, set iframe.src directly to sibling paths under the same .../nx_api/en-US/nxopen_net/ folder (e.g. namespaces.html, annotated.html for the class list, or namespace<Name>.html for a specific namespace) — this worked without needing to click through the accordion UI each time.
• Namespace pages use N<Name> prefixes in the tree (Doxygen convention); the ► marker means the namespace has visible sub-namespaces in the tree (e.g. ►NAssemblies has NXOpen.Assemblies.ProductInterface etc., mirroring the Java nxopen.assemblies.productinterface sub-package).

Top-level namespaces

All rooted at NXOpen (equivalent to Java's nxopen), or NXOpen.<Area> for sub-areas. This list matches the Java package list almost 1:1 (same underlying API, different language projection), with PascalCase names instead of Java's all-lowercase dotted names:

NXOpen (root/common — session, parts, geometry, features, base object model), NXOpen.AECDesign, NXOpen.ALP, NXOpen.AME (has sub-namespaces), NXOpen.AnimationDesigner (has sub-namespaces), NXOpen.Annotations, NXOpen.Appearance, NXOpen.Assemblies (has sub-namespaces), NXOpen.AutomatedTesting, NXOpen.BlockStyler (this is the .NET equivalent of Java's nxopen.uistyler — Block UI Styler runtime classes), NXOpen.BodyDes, NXOpen.CableRouter, NXOpen.CADCAEPrep, NXOpen.CAE (has sub-namespaces), NXOpen.CAM (has sub-namespaces), NXOpen.CLDKin, NXOpen.CloudDM, NXOpen.CollaborationApplication, NXOpen.Composites (has sub-namespaces), NXOpen.ContactlessInspection, NXOpen.DesignSimulation, NXOpen.Diagramming (has sub-namespaces), NXOpen.DiagrammingLibraryAuthor, NXOpen.Die, NXOpen.Display, NXOpen.DMU, NXOpen.Drafting, NXOpen.Drawings, NXOpen.DSE, NXOpen.DSEDesignWorkflow, NXOpen.DSEPlatform, NXOpen.ElectricalRouting, NXOpen.Facet, NXOpen.Features (has sub-namespaces — GeneralArrangement, StructureDesign, Subdivision, TopologyOptimization, VehicleDesign, mirroring Java's nxopen.features.*), NXOpen.Fields, NXOpen.Formboard, NXOpen.Gateway, NXOpen.GeometricAnalysis (has sub-namespaces), NXOpen.GeometricUtilities (has sub-namespaces), NXOpen.Implicit, NXOpen.Issue, NXOpen.Join, NXOpen.Layer, NXOpen.Layout2d, NXOpen.LineDesigner, NXOpen.Markup, NXOpen.MechanicalRouting, NXOpen.Mechatronics, NXOpen.MendixReporting, NXOpen.MenuBar, NXOpen.Mfg (has sub-namespaces — AM, MLP), NXOpen.MfgModel, NXOpen.MFGViewMaker, NXOpen.ModlDirect, NXOpen.ModlUtils, NXOpen.MoldCooling, NXOpen.Motion, NXOpen.OpenXml, NXOpen.Optimization, NXOpen.Options, NXOpen.PartFamily, NXOpen.PartMfg, NXOpen.PcbExchange, NXOpen.PDM (has sub-namespaces), NXOpen.PhysMat, NXOpen.PID, NXOpen.Placement, NXOpen.PLAS, NXOpen.PlasticDesigner, NXOpen.Positioning, NXOpen.Preferences (note: this is a distinct top-level namespace in .NET; Java exposes preferences via nxopen.options and per-app preference builders instead of a single package), NXOpen.PressLineSimulation (no direct equivalent seen in the Java package scrape), NXOpen.RegionRecognition, NXOpen.Report, NXOpen.Routing (has sub-namespaces — Electrical), NXOpen.RoutingCommon, NXOpen.Schematic (has sub-namespaces), NXOpen.Select, NXOpen.ShapeSearch, NXOpen.SheetMetal, NXOpen.ShipDesign, NXOpen.SIM (has sub-namespaces — PostConfigurator), NXOpen.StageModel, NXOpen.StageModelTemplate, NXOpen.StructureDesign, NXOpen.TDP, NXOpen.ToolDesigner, NXOpen.Tooling, NXOpen.UF, NXOpen.UIStyler (distinct from BlockStyler — lower-level UI Styler primitives, matches Java's nxopen.uistyler package name directly), NXOpen.UserDefinedObjects, NXOpen.UserDefinedTemplate, NXOpen.Utilities, NXOpen.Validate, NXOpen.VisualReporting, NXOpen.Vsa, NXOpen.Weld.

Namespace with no Java equivalent

• NXOpenUI — a top-level namespace (not nested under NXOpen) that appeared at the very end of the .NET namespace tree with no corresponding entry in the Java package scrape. Not yet drilled into; worth checking — likely a small .NET-only UI helper/interop namespace.

What's not covered yet

Class-level listings within each namespace were not extracted for this pass (same reasoning as the Java reference: root/common namespaces run into the hundreds of classes each). To pull a class list for a specific namespace: set the content iframe's src to .../nxopen_net/namespace<Name>.html (e.g. namespaceNXOpen_1_1BlockStyler.html — Doxygen encodes . as _1_1 in nested-namespace filenames), then read its summary table(s) the same way as the top-level namespaces.html page.