Critical Manufacturing DEE Debugger
Edit and debug Critical Manufacturing MES DEE Actions and custom business code in VS Code,
against a running MES host. Set a breakpoint, trigger the action, and step through the code the
host runs. Successor to the DEE Explorer add-in for Visual Studio.
Features
- Browse and edit DEE Actions as
.cs files with C# IntelliSense. Compile errors show
inline when you upload.
- Debug live: DEE Actions and your
Cmf.Custom.* business DLLs in one debug session.
- Any host: Docker, devcontainers, remote Docker, WSL, Kubernetes, OpenShift, or a local
process.
- Sync DEEs with your cmf-cli project (
Cmf.Custom.Data/DEEs) and commit them to git.
Requirements
- VS Code 1.145 or later. The Microsoft C# extension installs automatically.
- A development or test MES you can change, such as a
cmf dev local stack up stack.
- For containerized hosts, the
docker CLI.
⚠️ Development and test only. Debugging can pause the whole MES host. Never use it on a
production MES.
Quick start
Install Critical Manufacturing DEE Debugger from the
VS Code Marketplace
(a pre-release while the version is 0.x), or from a terminal:
code --install-extension CriticalManufacturing.cm-dee-debugger --pre-release
On a machine without Marketplace access, install the VSIX from GitHub Releases instead:
code --install-extension cm-dee-debugger-<version>.vsix.
Open your customization project, the folder that contains Cmf.Custom.Data/DEEs.
Select the DEE Debugger icon, then Discover Environments, pick your stack, and
Connect. When asked for credentials, use a Personal Access Token.
Open an action, turn on DEE Debug Mode, run Attach Debugger to MES Host, set a
breakpoint, and trigger the action.
For a guided walkthrough, run DEE Debugger: Open Getting Started, or follow the
30-minute tutorial.
Learn more
License
BSD 3-Clause © Critical Manufacturing. See LICENSE.md and NOTICE.md.
The extension sends no telemetry and talks only to the MES host you configure.
| |
