# Debug DEE in CM 11

**URL:** <https://community.criticalmanufacturing.com/t/debug-dee-in-cm-11/550>\
**Category:** Extensibility\
**Tags:** v11.3, business-rules\
**Created:** [July 17, 2025, 8:42pm UTC](https://community.criticalmanufacturing.com/t/debug-dee-in-cm-11/550 "2025-07-17T20:42:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cornalious\_Simon](https://avatars.discourse-cdn.com/v4/letter/c/cc9497/32.png) [@Cornalious\_Simon](https://community.criticalmanufacturing.com/u/Cornalious_Simon)\
**Post date:** [July 17, 2025, 8:42pm UTC](https://community.criticalmanufacturing.com/t/debug-dee-in-cm-11/550/1 "2025-07-17T20:42:37Z")

</div>

Hi Team,

I am creating DEE for CM 11. How to debug the DEE from my host visual studio to host container. Backend DLLs are debugging but DEE I am unable to do.

Thanks,

Simon C

---

<div class="post-metadata">

**Author:** ![Joao\_Moreira](https://avatars.discourse-cdn.com/v4/letter/j/b9bd4f/32.png) [@Joao\_Moreira](https://community.criticalmanufacturing.com/u/Joao_Moreira)\
**Post date:** [August 12, 2025, 11:16am UTC](https://community.criticalmanufacturing.com/t/debug-dee-in-cm-11/550/2 "2025-08-12T11:16:32Z")

</div>

Hi Simon,

Thanks for your question. We’re currently reviewing our tools and plugins for debugging containers, but in the meantime, here’s a reliable process you can follow to debug your DEE from Visual Studio to your host container.

This method allows you to debug your DEE code within the Actions DLL.

**Step-by-Step Debugging Process:**

1. 

**Adjust Your Custom Projct Actions Output:** In your “Debug” configuration for the Actions project, change the output folder to your `LocalEnvironment` folder. This will ensure that when you build your project, the DEE DLL is generated in the correct location. The DLL will be named something like `Cmf.Custom.MyProj.Actions.dll`.  
2.

**Launch Your Local MES Instance:** Start your local MES instance as you normally would.  
3.

**Edit Your DEE in the UI:** In the MES UI, edit your DEE’s Test and Action code methods. You’ll need to add a reference to your Actions DLL.  
4.

**Replace DEE Code with DLL Calls:** Update the code in both your test condition and action methods to call your DEE class directly from the DLL.

- 

**For the Test Condition:** `

```auto
(new CustomDeeToDebug()).DeeTestCondition(Input);

```

## `

**For the Action Code Execution:** `

```auto
UseReference("Cmf.Custom.MyProj.Actions.dll", "Cmf.Custom.MyProj.Actions");(new CustomDeeToDebug()).DeeActionCode(Input);

```

`

1. 

**Save and Make Effective:** Validate these changes, save your DEE, and make it effective in the system.  
6.

**Attach Visual Studio to the Container:** Now, attach your Visual Studio debugger to the container where your MES instance is running.

You should now be able to set breakpoints in your `DeeTestCondition` and `DeeActionCode` methods within the Actions DLL and debug your code as it runs in the container.

Once you’ve finished debugging, remember to revert your DEE code in the UI to its final, updated version.

Hope this helps!

João Moreira

---

<div class="post-metadata">

**Author:** ![rylan\_ruizhe\_wei](https://avatars.discourse-cdn.com/v4/letter/r/e56c9b/32.png) [@rylan\_ruizhe\_wei](https://community.criticalmanufacturing.com/u/rylan_ruizhe_wei)\
**Post date:** [December 25, 2025, 6:08am UTC](https://community.criticalmanufacturing.com/t/debug-dee-in-cm-11/550/3 "2025-12-25T06:08:06Z")

</div>

Super, it’s pretty useful tip, thank u.

---

<div class="post-metadata">

**Author:** ![system](https://yyz2.discourse-cdn.com/flex050/user_avatar/community.criticalmanufacturing.com/system/32/23_2.png) [@system](https://community.criticalmanufacturing.com/u/system)\
**Post date:** [August 21, 2026, 9:36am UTC](https://community.criticalmanufacturing.com/t/debug-dee-in-cm-11/550/4 "2026-08-21T09:36:17Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.