- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
링크가 복사됨
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Hello,
I just jump from CVF to IVF under visual studio .NET. I have the same problem (the variables that are passed to a subroutine appears in watch windows with dummy numbers. But the programs works well).
Is it fix now ? (do we need to install an update)
If it's not, can you explain more precisely the procedure you tell ?
Thanks
Gabriel
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
The particular problem with viewing host-associated variables is understood but not yet fixed. Work is in progress on this. As a workaround you can either:
1) Use the "context" dropdipown in Visual Studio to set the context to the caller where the variable is declared, or
2) If it's a module variable, use the syntax modname::varname in a watch window to view the variable
This works in most cases. We apologize for the inconvenience and hope to fix this soon.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Steve,
Has this been fixed in IVF 10.0?
Thanks and God bless!
jackosullivan
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
I just noticed that Steve is on vacation...
Does anybody know if this has been fixed in IVF10?
Thanks and God bless!
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Things are better (we think) but there are still some problems to be fixed and work is on-going to fix them. In those cases where we still don't get it right, Steve's work-arounds a few lines up should help.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Jeff,
Thanks for the quick reply and advice. I'm having trouble identifying what is meant by the "Context Dropdown" (using Visual Studio .NET 2003 Service Pack 1). I could find no reference to such in the Help. I was able to switch my way back and forth between the "contain"-ed subroutine and the "contain"-ing subroutine by using the "Call Stack" tab during Debugging. But that isa really tedious way to do things, especially when switching lines in the Call Stack causes the source view to switch to the calling line.
Have I been missing something?
Also, is there any way to sort the variables in the "Locals" window -- or some other window --that would let me locate the variable values quickly?
Thanks again for your help and God bless!
Jack O'Sullivan
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Sorry for the delay in replying; I'm on the road.
Yes, I believe Steve was referring to the Call Stack window. AndI know it's less than ideal; it's a work-around, not a solution. Be assured we wantthisfixed just as much as you do.
I don't know of any way to change the order in which Visual Studio displays variables in the Locals window. When I'm interested in just a few such variables, I use a Watch window.
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
Jeff,
Thanks very much.
I'll keep lighting those votive candles in front of St. Jude's statue that this problem gets fixed soon.("Saint for impossible causes", you know ;-)
God bless!
jack
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
- 신규로 표시
- 북마크
- 구독
- 소거
- RSS 피드 구독
- 강조
- 인쇄
- 부적절한 컨텐트 신고
