By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,758 Members | 1,247 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,758 IT Pros & Developers. It's quick & easy.

Why has debug.print stopped working???

P: n/a
Strangest thing, but, if I put debug.print statements in my code, they
simply get ignored when I run the project. Also, if I try to put a
breakpoint on a line containing debug.print, it jumps down to the next
available line of code when I run the project (or jumps down
immediately if the project is already running).

Another thing that's stopped working is the gray highlighting that
shows which blocks of code were played prior to the current one. Now
it's very difficult to answer questions like "who called this function
in the first place?"

The only thing I can think that could have caused these problems is
that I've added an installer to my solution (so the solution now
contains one main project and one installer project).

Ideas/suggestion/help greatly appreciated.

-Dan

Nov 9 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Check the compile configuration. If it is set to "Release", the debug class
doesn't get compiled.

Mike Ober.

"Daniel Manes" <da******@cox.netwrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
Strangest thing, but, if I put debug.print statements in my code, they
simply get ignored when I run the project. Also, if I try to put a
breakpoint on a line containing debug.print, it jumps down to the next
available line of code when I run the project (or jumps down
immediately if the project is already running).

Another thing that's stopped working is the gray highlighting that
shows which blocks of code were played prior to the current one. Now
it's very difficult to answer questions like "who called this function
in the first place?"

The only thing I can think that could have caused these problems is
that I've added an installer to my solution (so the solution now
contains one main project and one installer project).

Ideas/suggestion/help greatly appreciated.

-Dan

Nov 9 '06 #2

P: n/a
That's it! Thank you!

-Dan

Michael D. Ober wrote:
Check the compile configuration. If it is set to "Release", the debug class
doesn't get compiled.

Mike Ober.

"Daniel Manes" <da******@cox.netwrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
Strangest thing, but, if I put debug.print statements in my code, they
simply get ignored when I run the project. Also, if I try to put a
breakpoint on a line containing debug.print, it jumps down to the next
available line of code when I run the project (or jumps down
immediately if the project is already running).

Another thing that's stopped working is the gray highlighting that
shows which blocks of code were played prior to the current one. Now
it's very difficult to answer questions like "who called this function
in the first place?"

The only thing I can think that could have caused these problems is
that I've added an installer to my solution (so the solution now
contains one main project and one installer project).

Ideas/suggestion/help greatly appreciated.

-Dan
Nov 9 '06 #3

P: n/a
Hello!

So, then this is in the "build Output Path"...? If so, then just have
"bin\"...?

--
Thanks!
Soddy
"Michael D. Ober" wrote:
Check the compile configuration. If it is set to "Release", the debug class
doesn't get compiled.

Mike Ober.

"Daniel Manes" <da******@cox.netwrote in message
news:11**********************@m73g2000cwd.googlegr oups.com...
Strangest thing, but, if I put debug.print statements in my code, they
simply get ignored when I run the project. Also, if I try to put a
breakpoint on a line containing debug.print, it jumps down to the next
available line of code when I run the project (or jumps down
immediately if the project is already running).

Another thing that's stopped working is the gray highlighting that
shows which blocks of code were played prior to the current one. Now
it's very difficult to answer questions like "who called this function
in the first place?"

The only thing I can think that could have caused these problems is
that I've added an installer to my solution (so the solution now
contains one main project and one installer project).

Ideas/suggestion/help greatly appreciated.

-Dan


Nov 9 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.