Difference between revisions of "3.3 Debugging"
Jump to navigation
Jump to search
Abeloglazova (talk | contribs) |
|||
| Line 1: | Line 1: | ||
Sometimes an indicator or signal may not work properly. So it will require some additional debugging. This can be done in two ways: | Sometimes an indicator or signal may not work properly. So it will require some additional debugging. This can be done in two ways: | ||
| − | + | <ol><li> '''Using Microsoft Visual Studio.''' It is a good professional tool and it is much easier to debug the code there. The procedure is described in the following chapter: [[6. Integration with Microsoft Visual Studio 2010/2012/Express]]. | |
| − | + | <li> '''Without using a special debugger.''' In this case the default PLEditor .NET Editor can be used. It is possible to trace necessary values of variables to either a previously created file or to the Output of the editor by means of scripting language. </ol> | |
<syntaxhighlight> | <syntaxhighlight> | ||
#if DEBUG | #if DEBUG | ||
Latest revision as of 11:06, 26 August 2019
Sometimes an indicator or signal may not work properly. So it will require some additional debugging. This can be done in two ways:
- Using Microsoft Visual Studio. It is a good professional tool and it is much easier to debug the code there. The procedure is described in the following chapter: 6. Integration with Microsoft Visual Studio 2010/2012/Express.
- Without using a special debugger. In this case the default PLEditor .NET Editor can be used. It is possible to trace necessary values of variables to either a previously created file or to the Output of the editor by means of scripting language.
#if DEBUG
Output.WriteLine("CurrentBar = {0}; Close = {1}", Bars.CurrentBar, Bars.CloseValue );
#endif
