DevTracer
| $38.95 |
|
Description by Publisher
What is DevTracer?
DevTracer is a fast and effective tool for collecting trace
output. It can be used with many development platforms for Microsoft Windows, like
Microsoft Visual Studio and Visual Basic 6. It can also be used with scripting languages
like VBScript (Windows Scripting Host), and with web applications (ASP, ASP.NET)
Why DevTracer?
Some benefits when using DevTracer:
Create and collect trace output for desktop applications, distributed applications,
web applications, script ...
Unicode support
Tracing across process boundaries
Monitor tracing across network
Can be used with .NET and COM (Microsoft Component Object Model) compatible applications
Does not decrease the performance of the application
Applications using Devtracer do not depend on Devtracer, i.e. they will still run on machines without DevTracer (or part
of it) installed.
Monitor several applications simultaneously. For example: if you develop an ASP.NET
application and a Web Service consumed by the ASP.NET application, both can be monitored
at the same time.
Who can use DevTracer?
Basically every software developer writing software for Microsoft Windows can use
DevTracer. It does not depend on how you develop your software.
It can be used with all development tools targeting the Microsoft .NET platform,
and with all tools that support COM (Component Object Model).
DevTracer is also a great tool for testers. Whenever
they find a bug, they can use DevTracer to create some
trace information. This information they can send to the developer along with
the bug report, helping the developer to find the cause of the bug.
What is "tracing"?
Tracing is sometimes called creating diagnostic
output and is closely related to logging.
While logging is normally used to monitor the behavior
of an application after it has been deployed in a production environment,
tracing is used by software developers during development. It normally
displays more detailed information than logging.
Tracing is used to debug software, and to monitor it. Those
of you who already developed software for MS-DOS with C probably still remember
the function printf, which was the only way to debug
software (debuggers were rare during those days).
Nowadays debuggers are standard. But tracing is still extremely
useful, because it traces the execution of software. Testers normally do not use
a debugger (it is not their job), but they can record the trace
to make it easier for developers to find the cause of bugs, or other strange behavior.
Tracing is by no means a replacement for a debugger. It
complements debuggers.
How to Use DevTracer
Technical information can be found at here.
