Topics Search

Not stopping at Breakpoints in Debug mode

Not stopping at Breakpoints in Debug mode
Views: 19
I am using VS2010 with Win7 and VB.NET solution. Between, everything was working fine for months; the problem started yesterday.

The solution and the projects within it are set for Debug; I deleted the .suo file as recommended in one posting. I ran rebuild on each and every project individually and the entire solution.

I deleted the files in bin\Debug and did the whole thing over again. Still can't debug.

While stepping into (F8) I did get the hollow debug symbol in the margin and when just running the program (F5) the program starts up without stopping at any of several breaks in different functions and subs.
Sponsored Links:

Similar posts...

 

Cannot enter the project to debug mode

Cannot enter the project to debug mode Icon
I have a project that was download from the net. It is a open source project. I can run without anyerror with IDE 2005. But I cannot enter the debug mode. I have set the project build to debug. But I cannot still enter to debug.

I also got the following message when I run the project.

The following module was built with optimizations enabled or without debug information:
E:\Project.exe

To debug this module, change its project build configuration to debug mode. To suppress this message, disable the "Warn inf no user code on launch" debugger option
 

Form - Top of other forms

Form - Top of other forms Icon
I have application with toolbar. When I run the form in debug mode after completing debug form is not opened (Please see the screeshot attached). I need to close the form and open it again.Is there anyway to keep that form open in debug mode (Top of other forms)
 

VB 2010 Express, Windows 7 Debug Not Stopping On Error

VB 2010 Express, Windows 7 Debug Not Stopping On Error Icon
I've just installed Visual Studio 2010 Express on a new laptop running Windows 7 64 bit.

When I debug a VB project and an error is encountered a message is sent to the immediate window, but execution is not halted. This means I am unable to look at variables etc.

It's probably just an option I've missed.
 

Lost Menubar

Lost Menubar Icon
In VB 2010 after working on a form in design mode which has a menustrip and the form is taller than the IDE [Design] window and not returning to the top of the window before running in debug mode, the menu is eliminated from the menubar on the running form when the controlbox is set to False for the form and I could not access the menu.

After returning to design mode and scrolling to the top of the form and running debug, the menu returned. Is this a bug in the IDE or what?
 

VS2010 Service attaching to a remote debugger symbols will not load to set a breakpoint

VS2010 Service attaching to a remote debugger symbols will not load to set a breakpoint Icon
I have a Vb.Net 4.0 Windows Service. The service is setup to run in DEBUG with generate debug set to pdb-only.
Configuration is set to debug.

Installer project is set to DEBUG. VS IDE is set to debug.

I do a clean build and clean install of the DEBUG version. I run x64\msvsmon.exe on remote machine (W2008 R2 64bit). I attach to the process via workstation (XP PRO 32bit) in VS2010 without issue. Everything is set to debug but I get the infamous message breakpoint will not currently be hit,
 

Debug not working in 64bit

Debug not working in 64bit Icon
I've downloaded the 64bit debug symbols and told the IDE where they were located. But for some reason, VS won't build a 64bit debug EXE.

This is my first time doing 64bit so I never had to worry about it before. Is there something I need to do in the IDE that I don't know about? I went to Project Properties and set things to 64bit debug. But when I compile the program, it makes a 32bit program.
 

debugging in vb.net 2008

debugging in vb.net 2008 Icon
I want to step through VB.net 2008 project file. The code is executed from the postbuild command line. Thus this code is really executed during the build process.

Thus, can you tell me when I can do to debug this VB.net 2008 program that is executed from the command line? I know what to do is have the solution (ide) open, set breakpoints, set theproject as the startup file, and run the debugger.
 

I can't debug my code in VB6 IDE

I can't debug my code in VB6 IDE Icon
I'm trying to debug the code in VB IDE. This IDE is able to debug the console VB Scripts. But in our project, we are generating the HTML pages using the VB. We wrote the .cls modules for that.

When I try to debug this .cls modules, the control is not going to the particular code line. the properties of my project is alright.
 

Looking for help with DLookup and Dates

Looking for help with DLookup and Dates Icon
I've just started trying out DLookup (in Access 2003), and hadn't had any problems with it until I tried to use it with Date fields. If I use debug, it stops at statement with Date fieldDLookup, and gives me the following error

Run-time error "2001":
You cancelled the previous operation.

At that point I click on debug and the Date field DLookup line is highlighted. Here are a couple of lines of relevant code - the second is the Date field DLookup I am referring to

sComp = DLookup("[tcode]", "costs", "[rank]=" & iRank)
dDate = DLookup("[date]", "costs", "[tcode]=" & sComp)

I've checked various other values while in debug mode, and they all look fine.
 

Problem hovering a parameter in debug mode

Problem hovering a parameter in debug mode Icon
I am facing a very strange problem when hovering a parameter in debug mode. I have the following line:

Me.frmJobSub.Form.Filter = "custID=" & customerID
customerID stores the value “1”,
I am expecting the result to be:
Me.frmJobSub.Form.Filter = “custID=” 1

Strangely when I hover over the filter parameter I got:
Me.frmJobSub.Form.Filter = "[custID]= 20”,

Moreover, in the form side, the code is behaving correctly and filters record “custID=” 1

By the way, the "[custID]= 20” is an old code, written between brackets [custID]. I tried to compact and repair the database, delete the on_load event and recreate it again but with no progress.