vbCodeShield adds all this functionality to your projects at build time, meaning you don't have to wade through a mass of error handling code and line numbers whilst working in the development environment. Adding at build time means you can choose from a range of 'Build Plans' to support different error handling and debug requirements - full debug / call stack trace for isolating those really tricky bugs; error handling and object instance counting for your release version, for example.
Error identification
- Adds an error trap to every procedure
- Recognises and accommodates existing error handling logic
- Produces a variable dump (local, module and global)
- Parameter content dump
- Optionally encrypts logged error and context information
- Adds line numbers to ensure pin-pointing of an error to an individual line of code
Error logging
- Send email directly from error dialog (requires MAPI client)
- Error details copied to clipboard
- Error details logged to NT Event log (Windows NT / 2000 only)
Error diagnosis ('Intellifix')
- Optional feature to provide streamlined fault diagnosis and resolution, reducing the support load
- As soon as a fix or resolution is available and recorded, users encountering an issue will be aware immediately
- Complete Internet Information Server ASP application provided to allow over the internet on-line error reporting, diagnosis and even fixing
- Uses HTTP and configurable proxy information, so will bridge firewalls
- Can use SSL for information transmission
- Provides real time information to the user about fault status, resolution and fix information
- Allows users to request notification when a fault is resolved, reducing the load on support staff
- Provides a Microsoft style knowledge base article containing symptom, resolution and fix information instantly to users without them having to make a support call
- Provides direct links to fixes and patches when available, allowing instant resolution
Exception catching
- Converts GPFs and other exceptions to run-time errors trapped and logged by normal vbCodeShield error identification and diagnosis features
Run-time Call stack monitoring and logging
- Parameter contents included in call stack detail
Run-time debug message output and logging
- Existing Debug.Print statements automatically converted
SourceSafe integration
Automatic check-in and version labelling
Instance counting to identify objects that do not terminate correctly
- Identifies 'circular reference' scenarios
- Identifies precisely which classes are not terminating correctly
Extensibility
- Full source code for Error Handling object provided
- Can extended compile process with new plugins
- Can extend user interface with new plugins
- Can extend the Debugger with new views and monitors
Configuration
- Local error handler, variable and parameter dump code can be fully customised to individual requirements
- Combinations of features can be saved as 'Plans' which can be re-used across many projects
- Unlimited number of plans
- Allows project specific plans
Development team support
- SourceSafe integration
- Central Plans repository
- Configuration saved as a related document and therefore is portable with the source code and can be version managed using SourceSafe or other configuration management tool
Diagnosis and error handling features switched by registry parameters - minimum of runtime overhead
- Different components can have specific registry settings to customise error handling behaviour
Other Features
- Visual Basic and Visual Basic for Applications Integration
- Batch Compilation
- Real-time Debugger
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.