Hi Li,
>Suddenly IDE can't find the code changes I made. After run the program
>and step in, IDE only show old value and can't the new variables. When
>click to make the break point, it doesn't cover current line. the length
it
>covers is the length of old line that used to be here.
>...
Based on my understanding, the problem is when you edit your VB.NET program
and then debug it in the VS.NET 2003 IDE, it appears the IDE executes the
code before you edited,please let me know if I have misunderstood it.
Before diging into the problem, I want to know does this problem only occur
when you debug your program or all the time, I mean if you build a debug
(and a release) version program and run it outside the VS.NET IDE, which
code it executes, edited or unedited?
By the way, since the IDE has stepped into the unedited code, the project's
debug database file seems to be outdated, you may take a try on deletting
that program's PDB file(obj\debug\appname.pdb) and rebuild the project...
Thanks!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ??C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
Li Weng - 29 Mar 2005 14:09 GMT
Yes, it looks like the IDE executes the code before I edited.
Yes, I debug it in the VS.NET 2003 IDE.
I didn't try it outside the IDE. But it looks like after I run the program
(debug version)within IDE (it's a GUI, so it stays thare waiting input or
button click), and haven't step in yet (that's what you mean by debug?), it's
already wrong. At this time, when I click to set break point, the red color
bar shows it can't find the correct line, i.e., it only covers the old line
length.
My coworker tried deleting .pdb file and that didn't help.
Thanks in advance.
Li
> Hi Li,
>
[quoted text clipped - 31 lines]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
Gary Chang[MSFT] - 30 Mar 2005 08:45 GMT
Hi Li,
If you copy and edit the current project in another machine, is it OK?
And do you get the same problem when you work with some other VB.NET
project?
By the way,do you work on another source code file whose filename is just
as the same as the target file you debugged by any chance?
Thanks!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ??C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.
Li Weng - 30 Mar 2005 14:17 GMT
A team of three is working on the same solution and use sourceSafe to manage
it. All three PC has the same problem.
After we deleted some references and moved some references to local, it
looks like the problem is gone. But we don't know why.
If you see any cause from this please let me know. So I know how to handle
it next time. If not, that's ok. Anyway, it's ok now.
Thanks.
Li
> Hi Li,
>
[quoted text clipped - 19 lines]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
Li Weng - 30 Mar 2005 17:17 GMT
Hi, Gary:
That problem happens again!
Yesterday we checked in the changes and did reference deletion and moving,
etc. We got the change in IDE.
But today we checked out codes and made some changes and IDE doesn't see the
changes again!
Please help!
Thanks!
Li
> A team of three is working on the same solution and use sourceSafe to manage
> it. All three PC has the same problem.
[quoted text clipped - 30 lines]
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
Li Weng - 30 Mar 2005 22:29 GMT
I think we found out the problem.
One of our references has incorrect path so IDE stoped building and didn't
generate new .exe. When we run, we run the old version! So it didn't have the
changes. To try fixing it we removed the references and added again so
sometimes it got re-built and look like the problem is gone.
Thanks.
Li
> Hi, Gary:
>
[quoted text clipped - 43 lines]
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
Gary Chang[MSFT] - 31 Mar 2005 03:51 GMT
Hi Li,
Thank you very much for updating us you got the answer, it seems I haven't
considered the possibility that you use the Visual Source Safe to manage
the project:(
By the way, next time if you get any similar problem which could be caused
by Source Safe, I suggest you can also post it to the Visual Source Safe
newsgroup:
microsoft.public.visual.sourcesafe
microsoft.public.vsnet.vss
Have a sunny day!
Best regards,
Gary Chang
Microsoft Community Support
--------------------
Get Secure! ??C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn
This posting is provided "AS IS" with no warranties, and confers no rights.