property evaluation failed when doing quick watch

[grimrob]

I have upgraded to Visual Studio 2008 and frequently have the problem
where I cannot inspect properties of an object. Every property shows
up in the Quick Watch window showing "property evaluation failed".
This is repeatable on different machines so appears to be a common
problem to VS 2008. There was never a problem with the same classes in
VS 2005.

Does anyone know how to get around the problem?

 

[Mr. Arnold]

I have upgraded to Visual Studio 2008 and frequently have the problem
where I cannot inspect properties of an object. Every property shows
up in the Quick Watch window showing "property evaluation failed".
This is repeatable on different machines so appears to be a common
problem to VS 2008. There was never a problem with the same classes in
VS 2005.

No, it's not a common problem. I have been using VS 2008 for a long time,
and I have never seen it. Nor have I heard of the problem from other
developers using VS 2008.

Does anyone know how to get around the problem?

However, I did run into problems at a site a couple years back with the
usage of VS 2005 in the company with VS 2005, its IDE and debugging, with
lots of things would stop working and eventually the IDE would hang or VS
would crash, which was happening throughout the developer machines used.

It turned out that the page file size was too small on the XP machines
deployed to the programmers, and it was causing all of the problems. Once
the machines were configured to let XP automatically control the page file
size as it needed it, the problems went away.

I suspect that you have some type of configuration problems in some way, and
it's causing VS 2008 problems..



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4077 (20090514) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[Mr. Arnold]

I have upgraded to Visual Studio 2008 and frequently have the problem
where I cannot inspect properties of an object. Every property shows
up in the Quick Watch window showing "property evaluation failed".
This is repeatable on different machines so appears to be a common
problem to VS 2008. There was never a problem with the same classes in
VS 2005.

No, it's not a common problem. I have been using VS 2008 for a long time,
and I have never seen it. Nor have I heard of the problem from other
developers using VS 2008.

Does anyone know how to get around the problem?

However, I did run into problems at a site a couple years back with the
usage of VS 2005 in the company with VS 2005, its IDE and debugging, with
lots of things would stop working and eventually the IDE would hang or VS
would crash, which was happening throughout the developer machines used.

It turned out that the page file size was too small on the XP machines
deployed to the programmers, and it was causing all of the problems. Once
the machines were configured to let XP automatically control the page file
size as it needed it, the problems went away.

I suspect that you have some type of configuration problems in some way, and
it's causing VS 2008 problems..



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4077 (20090514) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

[grimrob]

No, it's not a common problem. I have been using VS 2008 for a long time,
and I have never seen it. Nor have I heard of the problem from other
developers using VS 2008.

Thanks. We got to the bottom of the problem and it's because we had a
function which had too many arguments! The total size of the arguments
exceeded 256 bytes. It works but stops debugging working. We reduced
the arguments and the problem was resolved.

 

[grimrob]

No, it's not a common problem. I have been using VS 2008 for a long time,
and I have never seen it. Nor have I heard of the problem from other
developers using VS 2008.

Thanks. We got to the bottom of the problem and it's because we had a
function which had too many arguments! The total size of the arguments
exceeded 256 bytes. It works but stops debugging working. We reduced
the arguments and the problem was resolved.