Pressing 'More Information' doesn't show anything in the Feb CTP

I have a webapplication. When there is an error, pressing the 'More
Information' doesn't show the stack trace. I have to look at the source
of the page to find out what is wrong.

Also, in January CTP, Visual Studio would stop the process at the right
spot and offer me the option to show the exception. This doesn't work
anymore. Is there anything I can do to help debug my application inside
Visual Studio?

Phil

In WPF apps VS always seems to break out inside a generated cs file. Not
the real point of the exception. I didn't run the Jan CTP so possibly it
was different, but behavior for me has been like this as long as I can remember.

As a work around I set "Debug" -> "Exceptions" -> tick "Thrown" beside "Common
Language Runtime Exceptions".

But be aware this will break on all exceptions, even those which are caught
and ignored.

> I have a webapplication. When there is an error, pressing the 'More
> Information' doesn't show the stack trace. I have to look at the
> source of the page to find out what is wrong.
>
> Also, in January CTP, Visual Studio would stop the process at the
> right spot and offer me the option to show the exception. This doesn't
> work anymore. Is there anything I can do to help debug my application
> inside Visual Studio?
>
> Phil
>

Douglas Stockwell wrote:
> In WPF apps VS always seems to break out inside a generated cs file. Not
> the real point of the exception. I didn't run the Jan CTP so possibly it
> was different, but behavior for me has been like this as long as I can
> remember.
>
> As a work around I set "Debug" -> "Exceptions" -> tick "Thrown" beside
> "Common Language Runtime Exceptions".
>
> But be aware this will break on all exceptions, even those which are
> caught and ignored.
>
>> I have a webapplication. When there is an error, pressing the 'More
>> Information' doesn't show the stack trace. I have to look at the
>> source of the page to find out what is wrong.
>>
>> Also, in January CTP, Visual Studio would stop the process at the
>> right spot and offer me the option to show the exception. This doesn't
>> work anymore. Is there anything I can do to help debug my application
>> inside Visual Studio?
>>
>> Phil
>>
>
>

My issue is that it doesn't even break inside generated code. It just
stops the debugging process. In Jan, I was at least able to use the
exception assitant to look at the stack trace.

Also, I can't find how to do your workaround, perhaps the type of
application disables it? What is also strange is that I did a 'break
all' and then I get an error saying that I can't break that type of
appolication. Not fun...

Any suggestions ?

Phil

> My issue is that it doesn't even break inside generated code. It just
> stops the debugging process. In Jan, I was at least able to use the
> exception assitant to look at the stack trace.
>
> Also, I can't find how to do your workaround, perhaps the type of
> application disables it? What is also strange is that I did a 'break
> all' and then I get an error saying that I can't break that type of
> appolication. Not fun...
>
> Any suggestions ?
>
> Phil
>

If you don't have that menu item you can probably add it by going to Tools
-> Customize -> Debug -> Exceptions...

- Doug