Re: Close but no cigar

PS So it's very much a command line experience for the moment ?
You can't call up the call stack window, double click on it and the source
code pops up - if it's on the machine ? Or hover over variables and their
value shows up as hovering help ? This seems puzzling because if VS.NET can
debug a C# app that's running under it, what's the difference ? Why the
degradation of the debugging experience ?

Just wondered ....

Adam.

"Jochen Kalmbach [MVP]" <nospam-Jochen.Kalmbach@xxxxxxxxx> wrote in message
news:eBBi5bI1FHA.1564@xxxxxxxxxxxxxxxxxxxxxxx
> Hi Oleg!
>>>A small note: you need to have full-memory dumps in order to get the
>>>manged meta-data...
>>
>> Yes, of course (or at least the relevant CLR data in the dump).
>> It applies to WinDbg as well, so if the OP can see the managed call stack
>> etc.
>> with WinDbg, VS.NET+SOS should also be able to show it.
>>
>> Jochen, I remember some time ago there were talks about adding support
>> for smaller managed dumps in CLR 2.0 / VS 2005.
>> Have you recently heard anything about it?
>
> Not yet, but I will ask someone from the product team (hopefully to get an
> answer this or next week).
>
> --
> Greetings
> Jochen
>
> My blog about Win32 and .NET
> http://blog.kalmbachnet.de/


.

Loading