Debugging CAE plugins

Generally, CAE and the standard plugins run in Windows / .net instead of Linux / mono without limitations. The same is also true for most of the enterprise and custom plugins known to us. However, there may be rare cases where execution of a plugin is limited with respect to its environment.

The CAE configuration file is basically exchangable between Windows and Linux, but it must be noted that whenever file system paths are in the configuration of a plugin, these must be adapted depending on the operating system. Also, command-line tools called from a CAE can have a different parameter syntax in both operating systems.

NOTE: When developing on Windows and deploying to Linux, it is a good practice to have the Windows version of the configuration file in the developing system and maintaining a Linux version on the server, which will not be overwritten on deployment, but rather edited by hand if necessary.

ATTENTION: Running CAE in a debugger will provide unpredictable results if, at the same time, another CAE process is running on the Cinnamon Server accessed by the debugger. Therefore, you must first stop CAE before starting the debugging session. Please consider starting CAE on the server again after you're done debugging.

Once you have stopped the server-based CAE process, you can open the CAE solution in Microsoft VisualStudio, compile, and then run it in the debugger.

If you prefer, you can also use MonoDevelop instead of Microsoft VisualStudio, but the solution and projects as stored on SourceForge at ​https://svn.code.sf.net/p/cinnamon/code/Client were not built with MonoDevelop in mind. Therefore, while the code will probably work, the projects might need some modifications.