|
We have 2 VB.Net 2008 programs.
They are not 'related'.
They are in separate folders.
If I change a module in 1 via VisStudio and save it, then the other gets
This File has been modified outside the source editor.
The module is NOT in the Solutions Explorer of the 'victum' program.
It happens on more than 1 module and both ways but it does not seem to be for all modules.
How can I stop this form happening???
|
|
|
|
|
QuickBooksDev wrote: The module is NOT in the Solutions Explorer of the 'victum' program.
Close Visual Studio. Start Notepad and open the module. Add the text "Hello world".
Open solution A in Visual Studio. See if it contains the text "Hello world". Do the same for solution B. Chances are, the text will appear in both solutions. Correct?
|
|
|
|
|
I see what you mean. The modules are there but not in the solution explorer.
So I should be able to just x out of the 'misplaced' modules and that should do it.
Amazing that these modules do not show up even when you show all files.
Or am I missing something.
THanks
|
|
|
|
|
QuickBooksDev wrote: 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 but does not put it into the solution explorer for some reason.
I have looked at the sln in notepad before. I even did a Win 7 search of the folder (but of course the win7 search is not reliable). It was not there.
Doing the find on the text then x-ing out of the windows does fix it.
|
|
|
|
|
QuickBooksDev wrote: 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.
Thanks
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
