CodeSite
The CodeSite Logging System gives developers a deeper view of how code is running, enabling a quick location of problems, ensuring that the application runs correctly.
The CodeSite Logging System gives developers a deeper view of how code is running, enabling a quick location of problems, ensuring that the application runs correctly.
When CodeSite was first introduced, it immediately changed the way developers find problems in their code. The CodeSite has been extended beyond the developer's workstation making it a complete application registration system. Today, CodeSite takes application logging and debugging to a new level, focusing on productivity, usability, registration capabilities, and developer implementation.
Overview
The CodeSite Logging System gives developers a deeper view of how code is running, enabling a quick location of problems, ensuring that the application runs correctly. CodeSite logging classes allow developers to capture all kinds of information while their code is executed and then send that information to a live view or to a log file. In addition, the two registry styles, live and file registration, can be performed locally or remotely (via TCP, UDP, or HTTP).
A key element to the effectiveness of CodeSite is that, unlike message boxes and inspection variables at breakpoints, CodeSite messages are not transient. Message logging provides valuable information for locating problem areas in your code. Additionally, sending codesite messages does not interrupt the flow of the application, as happens when message boxes and breakpoints are used. As a result, CodeSite is much more effective in situations where user interactions (for example, focus changes) and paint problems need tracking.
CodeSite also addresses several shortcomings with traditional registration/tracking solutions. For example, CodeSite allows the registration of complex data structures and is not limited to simple strings. CodeSite provides more control over what is registered and when. Rather than relying on arbitrary record levels, separate registers are used for categorizing CodeSite messages. CodeSite also gives developers more flexibility in managing their registration information, such as allowing multiple applications (or multiple instances of the same application) and sending registry information to the same registry file. In addition, CodeSite viewers designed specifically for the analysis of registry messages are equipped with comprehensive and easy-to-use tools for analysis.
There are three main components to the CodeSite Logging System:
The main log class that developers use is T | CodeSiteLogger. (However, in most cases, manual construction of a Class T instance by developers is not required.)
In this way, the CodeSite log builder instance can be used immediately. In Delphi, CodeSite is a global instance of the TCodeSiteLogger class. In .NET, CodeSite is a static class that uses an internal instance of CodeSiteLogger.
The log information simply involves calling t-class methods | CodeSiteLogger. Most of the time, the overloaded Send method will be used. In its simplest form, a simple string message is sent. Other forms include submitting numeric data types, dates and times, objects, collections, bitmaps, and more.
O Dispatcher CodeSite
The primary log method in T | CodeSiteLogger is called Send because it describes more accurately what happens to the information being logged. In particular, T CodeSiteLogger instances send registration information to the CodeSite Dispatcher application, which runs in the background and is responsible for dispatching CodeSite registration messages to the final destination.
There are two basic destinations for CodeSite messages: a CodeSite Live Viewer (see below); and a CodeSite log file. However, these two target types can reside locally or on a remote machine. In addition, there are several ways for the CodeSite Dispatcher to transport messages to the final destination. The location of the viewer or log file, as well as the transport details to be used by the Dispatcher, are contained in a T-| CodeSiteDestination, which the CodeSite Dispatcher receives from each T-|
CodeSiteLogger.
In addition to its dispatch responsibilities, the CodeSite Dispatcher also allows dynamic blocking of selected CodeSite message types and even selected categories. In addition, the Dispatcher manages a list of symbolic paths that can be used as a reference by t-| CodeSiteDestination.
CodeSite viewers
The CodeSite Logging System comes with two viewers: codesite live viewer and codesite file viewer. Developers will most often use CodeSite Live Viewer, which is updated immediately when new CodeSite registration messages are received from the CodeSite Dispatcher. As a result, Live Viewer is required for real-time registration.
During file logging, the CodeSite Dispatcher writes the messages it receives directly to a CodeSite log file. However, even with the file log, viewing the contents of the file is required. Although log files can be uploaded to Live Viewer, this is not always practical, especially if Live Viewer is being updated during a real-time log session. In addition, there are features in Live Viewer, such as scratch pad, that are applicable only for real-time registration. As a result, CodeSite File Viewer is associated with the CodeSite log file extension (.csl).
Both viewers include a wide variety of inspectors and other tools specifically designed for analyzing CodeSite messages. For example, Message Organizer can analyze log messages and automatically create the appropriate views for isolating messages from the same application, category, segment name, etc.
Characteristics
CodeSite supports a wide variety of development tools, languages, and frameworks. Specifically, CodeSite supports the development of Win32 and the Microsoft .NET Framework in the Embarcadero and Microsoft integrated development environments.
System Requirements
You don't know what software you need or you haven't found what you were looking for? We have a team ready to help you choose the right software for your company.