can't debug!

[Lord Zoltar]

I finally got around to taking VS 2008 beta for a test spin, and I
can't debug! I add a breakpoint to any line in my application, and
when I hit "Debug", my program starts, and then immediately ends,
skipping the breakpoint. It's probably a config setting somewhere, but
I've never seen anything like this before. I've been looking for hours
but can't seem to find any way to fix it.
Anyone got a suggestion?

[RobinS]

Make sure your build configuration is set to Debug instead of Release.

RobinS.
--------------------------
"Lord Zoltar" <lo*********@gmail.comwrote in message
news:bb**********************************@q78g2000 hsh.googlegroups.com...

>I finally got around to taking VS 2008 beta for a test spin, and I
can't debug! I add a breakpoint to any line in my application, and
when I hit "Debug", my program starts, and then immediately ends,
skipping the breakpoint. It's probably a config setting somewhere, but
I've never seen anything like this before. I've been looking for hours
but can't seem to find any way to fix it.
Anyone got a suggestion?

[=?Utf-8?B?TW9ydGVuIFdlbm5ldmlrIFtDIyBNVlBd?=]

If you are using 64 bit XP or Vista, breakpoints won't work unless you
compile the program for x86 CPU (don't ask me why, but this goes for
Edit-And-Continue as well.) Use the Configuration Manager in the solutions
properties to change targetted CPU.

--
Happy Coding!
Morten Wennevik [C# MVP]
"Lord Zoltar" wrote:

I finally got around to taking VS 2008 beta for a test spin, and I
can't debug! I add a breakpoint to any line in my application, and
when I hit "Debug", my program starts, and then immediately ends,
skipping the breakpoint. It's probably a config setting somewhere, but
I've never seen anything like this before. I've been looking for hours
but can't seem to find any way to fix it.
Anyone got a suggestion?

[Lord Zoltar]

On Feb 18, 12:27*pm, Morten Wennevik [C# MVP]
<[e-mail]:

If you are using 64 bit XP or Vista, breakpoints won't work unless you
compile the program for x86 CPU (don't ask me why, but this goes for
Edit-And-Continue as well.) Use the Configuration Manager in the solutions
properties to change targetted CPU.

No, it was regular 32-bit XP. I had the build set to Debug. It would
happen with even the simplest of all "Hello World!" forms
applications.
But I've been out of the loop for a while, as I had no idea that VS
2008 was out now, past beta. I guess I'll have to download the trial
version or express edition and see if that solves the problem.

[Lord Zoltar]

On Feb 19, 12:35*pm, Lord Zoltar <[e-mail]:

On Feb 18, 12:27*pm, Morten Wennevik [C# MVP]

<[e-mail]:

If you are using 64 bit XP or Vista, breakpoints won't work unless you
compile the program for x86 CPU (don't ask me why, but this goes for
Edit-And-Continue as well.) Use the Configuration Manager in the solutions
properties to change targetted CPU.

No, it was regular 32-bit XP. I had the build set to Debug. It would
happen with even the simplest of all "Hello World!" forms
applications.
But I've been out of the loop for a while, as I had no idea that VS
2008 was out now, past beta. I guess I'll have to download the trial
version or express edition and see if that solves the problem.

So I got around to installing C# express and I am still having the
same problem: I create a new windows Form app, and add a breakpoint to
the InitializeComponent() line and when I run the debugger, it breaks
at that line. When I hit resume, the app end. When I don't have the
breakpoint, the application doesn' teven run.
Any ideas why this is happening?