Persistent breakpoints [ All Languages » VB »  Language] Total Hit ( 3278) Rate this article:     Poor     Excellent   Submit Your Question/Comment about this article Rating

When you close a VB IDE session, VB saves the code but doesn't save the current set of breakpoints. If you need (non-conditional) breakpoints to persist among sessions, don't use the F9 key. Instead, use the following statement Click here to copy the following block Debug.Assert False The above code will always stop the execution flow when the program is running in interpreted mode, but has no effect when you then compile to an executable file. Exactly as real breakpoints do.

Related Article(s)

Submitted By : Nayan Patel  (Member Since : 5/26/2004 12:23:06 PM)
	Job Description : He is the moderator of this site and currently working as an independent consultant. He works with VB.net/ASP.net, SQL Server and other MS technologies. He is MCSD.net, MCDBA and MCSE. In his free time he likes to watch funny movies and doing oil painting.
View all (893) submissions by this author  (Birth Date : 7/14/1981 )