Hi,
as written in another forum topic we have issues debugging certain DEEs triggered in specific ways (assumed non-gui).
To check the incoming parameters or simply to “dumb debug” our code it would be nice to have some simple way to spit out information from inside of the DEE.
A “GUI”-triggered DEE can simply “throw new Exception(string)” which is not the best but at least usable.
A non-“GUI” triggered DEE of course cannot use that as there is no “website output”.
We do prefer to not develop on the host system itself but on our computers with that CMF-VisualStudio extension (and remote debugging being.. not properly working for all things you will develop). So a “dumb debug” (you know … printing out stuff to see where “it has gone into” etc - like when not having a debugger at all) would be what could be a viable solution.
We do not have an easy access to read the Hosts CMF-log files (also they grow quite big if you plan on spitting out a lot of lines). Means it would be good to avoid having to use a storage option the host can read but a user (which has extended rights in the MES site, but not the MES host system) can not read.
How do you approach it? Is there some kind of “console log” which can be visited via the MES website? Some UIPage with a “live” output ?
If you have some smart idea: please share it with us.
Thanks in advance,
Ronny