A key element to CodeSite's effectiveness is that unlike message boxes and inspecting variables on breakpoints, CodeSite messages are not transient. The resulting log of messages provides valuable information for locating problem areas in your code.
In addition, sending CodeSite messages does not interrupt the flow of your application as happens when message boxes and breakpoints are used. As a result, CodeSite is much more effective in situations where user interactions (eg. focus changes) and painting issues need to be tracked.
CodeSite also addresses several shortcomings with traditional logging/tracing solutions. For example, CodeSite allows logging complex data structures and is not limited to simple strings. CodeSite also provides more control over what gets logged and when.
Instead of relying on arbitrary logging levels, separate loggers are used to categorize CodeSite messages. CodeSite also gives developers more flexibility in managing their logging information such as enabling multiple applications (or multiple instances of the same application) to send logging information to the same log file.
In addition, the CodeSite viewers, which are designed specifically for analyzing CodeSite logging messages, provide extensive, easy-to-use tools for analysis.
- Embarcadero RAD Studio 2010 (Including Delphi 2010, C++Builder 2010, Delphi Prism 2010)
- CodeGear RAD Studio 2009 (Including Delphi 2009 & C++Builder 2009)
- Visual Studio 2008
- CodeGear RAD Studio 2007 (Including Delphi 2007 & C++Builder 2007)
- Borland Developer Studio 2006 (Including ALL Turbo Editions)
- Visual Studio 2005
- Delphi 2005
- Visual Studio .NET 2003
- Delphi 5, 6, and 7
- C++Builder 5 and 6