Language Wrappers

On this page

Add CAD features where your application already lives

An engineering application may already manage orders, inspection results, or manufacturing data. Users still need to open and work with the CAD models behind those records. OCCT3D language wrappers bring CAD operations into C# and Java products, helping your team connect geometry with the work people already do.

Use them to extend a viewer, add model processing, or build a conversion workflow around your team’s existing skills.

How it works

Call CAD operations from your application’s language, then connect model data and results with its interface. A user action can open a file, display a part, or run a geometric calculation. Your application decides how the result appears and what users do next.

For example, selecting a component could open its part record. A measurement could become part of an inspection report. A reviewed model could pass to a later preparation or export step.

Choose C# or Java for your application

The C# Wrapper connects OCCT operations with .NET applications. It lets a C# team build CAD interaction alongside existing forms, documents, and reports.

Java interfaces bring CAD operations into Java applications. A team can connect geometry processing with its established engineering tools and data services.

Both routes help developers work in a language they already use while adding CAD features to their product.

Bring geometry into everyday decisions

A model becomes more useful when users can inspect it beside the information driving a decision. A quoting tool can show the part under discussion. An inspection application can place geometry beside recorded findings. A supplier portal can prepare an incoming file for review.

Choose CAD readers and writers for the files your users exchange. Keep available part names, colors, and placements with the geometry so people can identify the model items involved.

Connect CAD work across established product teams

A business may use a C# desktop tool for engineering review and a Java service for file preparation. Without a shared approach, teams can repeat the same model-handling work in separate products.

Language wrappers let each team connect OCCT operations with its own application. They can organize work around common tasks, such as loading a supplier model, measuring a part, or preparing geometry for another tool. Representative models give both teams a practical way to compare the results users depend on.

This helps managers plan useful CAD features alongside ongoing product development. Each team keeps its existing interface and business process, with geometry available where users need it.

Build around your next CAD task

Add model preparation with Shape Healing & Validation or surface meshing with Advanced Mesher. Connect these steps with review, reporting, or conversion in your application.

Tell us what your application should do next, with an example model and the result your users need.