dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Visual Basic
Expertise: Beginner
Oct 21, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Insert Persistent Breakpoints

VB won't let you save a breakpoint when you have a lengthy debugging session. Use Debug.Assert to create persistent breakpoints that trigger when you are in the environment, but not in the compiled program. Just insert "Debug.Assert False" where you want the breakpoint.

This technique is also useful to ensure different branches of the code are debugged. When coding, insert these persistent breakpoints in every section of the code you know needs to be tested by stepping through it, and delete the breakpoints once you have verified that the section works as intended.

Tore Bostrup
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date