A Debugging/Profiling Add-In by Innovasys

There are a number of tools that share some of the goals of vbCodeShield available today (most notably Compuware Failsafe). Why choose vbCodeShield over competitive products ? We recommend you consider several questions when choosing your error handling solution:

Does the tool require that you work with a mass of template error handlers whilst developing?

vbCodeShield does not, all code is added as a seamless part of the build process.

Does the tool support Email, Event log, Disk log and on-line error reporting?

vbCodeShield does. What's more, the full source code of the error handler component is provided so can be extended or modified as required.

Does the tool add value to the service you give your customers?

Many competitive tools offer little more than the standard VB error messagebox to the customer - vbCodeShield allows the customer to submit notes, provide contact details, request notification when the issue is resolved and access instant on-line diagnosis, fix and workaround information where available;

Does the tool add real value to your support process?

vbCodeShield provides a uniquely rich set of context information as part of every error report, enabling the precise line of code that failed to be identified, and includes the contents of variables at point of failure. By posting workaround and fix information for reported errors, subsequent users reporting the same error on-line get available information without requiring the assistance of support individuals. Support costs are reduced, incident resolution time is dramatically improved.

Does the tool work with existing error handlers?

vbCodeShield allows your existing local error handlers to carry on working unmodified, whilst unexpected or unhandled errors are trapped and reported.

Is the tool really configurable?

vbCodeShield allows to completely reconfigure the native error handling and debug mechanisms and to easily organise the features you wish to implement using a system of 'Build Plans'. Every project can use a standard or custom Build Plan. Error handling and reporting functionality is encapsulated in an error handling component to which you have full source code.