asked on

debugging an application for deployment, advice?

I'm about to deploy my first VB application to a customer... I need some advice.

I am attempting to do extensive beta-testing before I deploy the application and would like to know how I should perform this from others who have done it.

First, I placed in each function/subroutine:

function doSomething
on error goto doSomethingError

'whatever I put in the function
exit function
doSomethingError:
Msgbox "Error found at doSomething " & err.Description
end function

is this the best way to catch errors during the testing phase and during the release?

Also I will have a few other individuals testing the application on different computers since I know that being the developer I probably am used to running it a particular way and they can find things I won't think of. What else can I do to make sure the deployment is successful? Is there anything else in VB I should implement that will be very good to have before or during deployment? Please let me know. I have completed a java application before that worked great on release but I'm still kind of new with VB stuff so in a sense you can consider me a beginner on deployment in VB. ;-) thanks for any advice

guid

ASKER CERTIFIED SOLUTION

1markmc

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

guidway

ASKER

one more question (I'll raise the points since this is an add-on question). Should I use the native VB errors in the subs/functions or raise my own using Err.Raise ?

just curious which is better... thanks

guid

guidway

ASKER

I'll give time for anyone else to comment with ideas and close this tomorrow morning... thanks to any who respond. I appreciate it!

guid

SOLUTION

rettiseert

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

MADisonMAN

membership