Ok how can this be???

  • Thread starter Thread starter Lloyd Sheen
  • Start date Start date
L

Lloyd Sheen

I am now in one of the those VS2008 twilight zones. I simply run my program
and the breakpoints show as "Source code is different that original
version". I made no changes. I then rebuilt. Same thing.

Ok then lets get out of the car and back in. VS's equivalent is Clean
Solution. Why does this happen??

Is there any way other than constantly "cleaning". I hire a service to this
at my home, think I can get them to do it???

LS
 
Lloyd Sheen said:
I am now in one of the those VS2008 twilight zones. I simply run my
program and the breakpoints show as "Source code is different that original
version". I made no changes. I then rebuilt. Same thing.

Ok then lets get out of the car and back in. VS's equivalent is Clean
Solution. Why does this happen??
Click to expand...

So, does "Clean Solution" and rebuilding actually solve the problem?
 
Herfried K. Wagner said:
So, does "Clean Solution" and rebuilding actually solve the problem?
Click to expand...

A qualified yes. A while ago I asked here and in the VS forums if there was
a place where items were cached. I thought there had to be since opening
the .vb source files have no indication of which items are opened/closed as
far as outlining etc. I was also have a problem that eventually if I made a
change to my main form it would generate bad code in the source.vb file for
several event handlers for usercontrols which were hosted on the main form.
The code generated was bad and I had never seen VS 2008 do that before. I
had to delete the code and then clean the solution to get rid of the problem
(it would / and will) come back again after a certain number of updates to
the solution (or files in it).

I think Clean is like the MS uninstaller cleanup utility. Rather than fix
the problem they have given a tool to fix the problem.

LS
 
Back
Top