VB Watch v2: Profiler, Protector and Debugger for VB6
Take cover from run-time errors. Test, debug and profile your code.
Increase the quality, stability and performance of your Visual Basic 6.0 programs.
VB Watch is three tools in one: Profiler, Protector and Debugger.
Profiler measures performance and test coverage.
Protector implements robust error handling.
Debugger helps monitor your executables.
|VB Watch Profiler
||VB Watch Protector
Measure speed and coverage
Where are the bottlenecks? VB Watch Profiler lets you measure execution speed.
See what procedures are the slowest ones, and which lines or loops are taking
up most of the time. Or measure execution times before and after your enhancements.
Test coverage. Are you sure you tested all your code?
VB Watch Profiler records your tests as you execute them.
It shows you in red what procedures and lines are still untested.
Make sure you've tested all the Select Case branches and nested If..Then..Else's too.
The best error handling ever
No more mysterious error messages and crashes!
No more yelling users! Find bugs the easy way.
VB Watch adds advanced error handlers to your code with a few clicks, keeping
your existing handlers fully enabled.
Error messages can include: error description, procedure name, line number,
parameter and variable values, object properties, call stack,
run-time library versions, and
even execution trace procedure-by-procedure, line-by-line.
Have the users email all this info immediately when an error happens.
This is the fastest way to fix bugs ever discovered.
Stop guessing - VB Watch tells you exactly where the bug is lurking!
|VB Watch Debugger
||VB Watch Console
Trace compiled apps
Why debug compiled code?
This is the way to do it when you're creating ActiveX controls or writing code for
web browsers or Microsoft Transaction Server.
Does your code behave as it should when compiled?
Trace the procedure calls and executed code lines in your compiled apps. Even
better, monitor and pause your app. See its status. What line is it on?
What procedures were called with what arguments? Call stack? Which objects are alive?
What global variable values are in effect?
Setup breakpoints to your exe, dll or ocx and see what's really happening in it.
Debugger allows remote debugging at client site via TCP/IP.
Automate VB Watch
The instrumentation console allows you to batch process projects with predefined settings.
The Console works together with Profiler, Protector and Debugger. Run the Console to instrument one or more projects in a batch.
You can also call the console from a batch file to add error handling in a fully automated way each time right before you release your program.
VB Watch v2 works with Visual Basic 6.0. It does not support other languages such as VBA, VB.NET or C#.
All generated code is 100% pure VB source.
You don't need to distribute any extra run-time libraries,
unless you use some advanced Protector features.
How to use
Learn the benefits of VB Watch.
Browse the help to learn the details of VB Watch.
The free demo is fully functional for projects with up to 10 source files.
Extend the demo
Get a key to use the demo on your larger projects.
Windows 95/98/NT/2000/XP/Vista/7. Visual Basic 6.0. No support for VB.NET or VBA.
VB Watch editions
VB Watch comes in two editions: Standard and Pro.
|Standard Edition||= Profiler + Protector|
|Pro Edition||= Profiler + Protector + Debugger + Console + Profiler reports + Profiler data export|
VB Watch editions
||Measure performance and test coverage.
|Profiler reports & export
||Report and export profiling data.
||Add error handling.
||Automate instrumentation process.
|Price for single user
Licensing is per developer. Run-time royalty free for users of your own software.
Single user license permits one person to use the software on one
or more computers.
Team license equals 5 single user licenses. 10-pack equals 2 team licenses.
Site license covers any number of users in a single organization
within a radius of 3 miles (5 km).
Run-time files installed with VB Watch v2:
gksui16.exe 1.73.236 (uninstaller file),
vbwFunctionsVB6.dll 22.214.171.124, zlib.dll 126.96.36.199.
Visual Basic 6.0 required.
Implement exception handling. Add line numbers. View call trace. Report call stack and variables. Debug. Profile code to find performance bottlenecks. Measure test coverage.