This is driving me crazy.
I have a rather large project that I am trying to modify. I noticed earlier that when I typed DbCommand
, visual studio did not do any syntax highlighting on it, and I am using using System.Data.Common
.
Even though nothing was highlighted, the project seemed to be running fine in my browser. So I decided to run the debugger to see if things were really working as they should be.
Every time the class that didn't do the highlighting is called I get the "the source file is different from when the module was built"
message.
I cleaned the solution and rebuilt it several times, deleted tmp files, followed all the directions here Getting "The source file is different from when the module was built.", restarted the web server and still it tells me the source files are different when they clearly are not.
I cannot test any of the code I have written today because of this.
Visual Studio. File formats category - v • e edit. Visual Basic source files are files that contain Visual Basic source code. There is no distinction between source files created by VB 6.0 and below and by Visual Basic 2003 and higher.
A source file consists of an optional set of option statements, import statements, and attributes, which are followed by a namespace body. The attributes, which must each have either the Assembly or Module modifier, apply to the .NET assembly or module produced by the compilation.
I got this issue running a console app where the source that was different was the source that had the entry-point (static void Main). Deleting the bin and obj directories and doing a full rebuild seemed to correct this, but every time I made a code change, it would go out-of-date again.
The reason I found for this was:
(For #2 -> accessible via the toolbar under the 'Debug/Release' drop down list.)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With