I see what you mean. The modules are there but not in the solution explorer.
That could happen when the module is in an assembly that's registered in the GAC, taking precedence over another copy. That doesn't explain why the IDE picks the code up as "changed".
Open the solution file (.sln, in the root of the project-directory) in notepad, and verify that it ain't the same files. Now and then I make a "link" instead of a copy when adding a file from another project - changing the file in one project would then cause the other IDE to "see" the changes and ask whether it should reload.
I think it happens if you double click on a file that goes to VisStudio. It adds the file to the solution
Not on my machine; had a solution open, double-clicked on a non-related sourcefile from another project. It opened, could be edited, but was not added to the solution, nor is the filename mentioned in the solution-file.
I have seen this before. I have a solution open and I want to view a vb module with notepad but I double click on the modules and it defaults to Vis Studio. That module is not 'in' the solution that I have opened. I have since changed the default program on .vb, etc. to Notepad but this is a 'new' machine and for the first few weeks it was not set.
Well I have no other idea how a module not related to a program can get into it, not be in the solution explorer.
Anyhow, you have help me solve the problem.
Last Visit: 31-Dec-99 18:00 Last Update: 28-Jul-16 5:10