Subject:variables, functions quirky with 4.5.103e Author:David Rees Date:16 Oct 2002 11:04 PM
FYI, I was seeing this with 100k as well.
When I type a variable in a watch I am not getting its value. Instead I get nothing. I also can't do functions on variables (which is what I really want to do).
Find attached three screen shots.
(1) I just started debugging. The watches on variable actually have their values - but the variable entries do not (for those variables that also have watches).
(2) Next I type in the $webService variable. At that point, all the watches on variables disappear.
(3) This just shows I can do non-variable watches just fine.
Subject:Re: variables, functions quirky with 4.5.103e Author:Minollo I. Date:16 Oct 2002 11:38 PM
We can see some problem similar to what you are describing when using
processors different from the built-in; we are investigating.
Please note that one current limitation of the MSXML .net processor is that
it doesn't correctly report global variables; we are working with Microsoft
to solve the problem.
About the crash, we are a bit puzzled about the information found in the
log. The problem seems to have happened while displaying the popup menu on
the watch window; was the application being killed at that point?
Subject:Re: variables, functions quirky with 4.5.103e Author:David Rees Date:17 Oct 2002 12:33 PM
No it wasn't being killed.
I am wondering if that is due to something on my machine. I have seen problems with popups in some of my company's tools as well on occasion. I get a "disposed component" when trying to open menus and so forth. I am thinking that somehow Win2K has run out of "GUI resources", but I thought that didn't happen in Win2K.
So its probably not your issue, but if you have any suggestions I sure would like to hear them.
thanks,
dave
PS, I appreciate the quick response you guys always show in these forums.
Subject:Re: variables, functions quirky with 4.5.103e Author:Minollo I. Date:17 Oct 2002 05:01 PM
We have fixed a few issues related to evaluation of variables in the watch
window when using XalanJ or Saxon.
We haven't been able to find problems when working with MSXML .net except
the issue mentioned earlier (unable to resolve global variables).