Re: Cannot evaluate expression. WTF?
- From: "Stevanich" <dotneticated@xxxxxxxxxxxxxxxx>
- Date: Mon, 24 Sep 2007 00:27:50 -0400
Rüdiger,
While I am not sure why this is happening, I wouldn't recommend using
Console.WriteLine. Try Debug.WriteLine, as those statements will be
stripped in a release compile.
Make sure you are doing a build before you run the debugger as well.
Hope this helps,
Steve - dotneticated.com
"Rüdiger Klaehn" <rudi@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:1189590434.552285.149140@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi everybody,
I have a major problem when working with VS.NET 2005 debugger on large
projects. Very often, the debugger is not able to evaluate any watch
expressions for no apparent reasons.
The code is compiled in debug mode, and all I want to do is to
evaluate some expression at a normal break point. No Exceptions,
Assertions or Stack overflows are involved.
The project in question is quite large and contains some constructs
like classes that are inner classes of other classes with type
parameters, like this:
class A<T> {
class B {
}
}
I had this happening whenever projects exceed a certain size or
complexity. But having a debugger that only works for Hello World
sized projects does not do me any good.
Is there any solution to this problem? I am back to littering the code
with Console.WriteLine statements because of this. My system is a quad
core with 4GB of ram, so it is obviously not a performance problem.
And no, reinstalling VS.NET is not a solution. I had this happening on
multiple machines. When I reinstall, it will probably work OK for a
few days, and then break again. I am not going to reinstall VS.NET
every two days!
By the way: I had this happen with many technologies like designers
and code generators that are supposed to make the developing process
easier. They always work just fine for tiny test projects, but once
you rely on them for large real world projects they break down at the
worst possible moment.
any help would be greatly appreciated,
Rüdiger Klaehn
.
- References:
- Cannot evaluate expression. WTF?
- From: Rüdiger Klaehn
- Cannot evaluate expression. WTF?
- Prev by Date: Re: stored procedure debugging, watching temp tables
- Next by Date: Re: step in .NET makes vs2005 freeze when unmanaged code is enabled
- Previous by thread: Cannot evaluate expression. WTF?
- Next by thread: Breakpoint ignored
- Index(es):
Relevant Pages
|
