CODEWITHSUNDEEP
visual-studiovisual-studio-2008filereload
Christian Klauser
Christian Klauser

Reputation: 4466

VS2008: Disable asking whether to reload files changed outside the IDE

I have a Visual Studio 2008 project where some code files are generated with each build (a parser, integrated via MSBuild aka editing the *.csproj file). VS does not know about the generated nature of these files (i.e. they are not the result of a "Custom Tool). So they "change" with every build, naturally. And VS2008 asks me after every build if I would like to reload those files:

This file has been modified outside the source
Do you want to reload it?

That would be ok if I had one of those files opened and in front of me, but I get these modal dialogs even with none of the code files opened.

So my question is: Is there a way to disable this dialog, per project, per solution or globally?

Thanks!

Upvotes: 19

Views: 13343

Answers (5)

JamesIngold
JamesIngold

Reputation: 374

This is an old post, but what worked for me was slightly different and I wanted to share:

This file has been modified outside the source

Go to Tools -> Options -> Debugging -> General and uncheck "Require source files to exactly match the original version". This allows you to use source code which is not the same as original version.

Upvotes: 0

Tim Sylvester
Tim Sylvester

Reputation: 23138

For VS2008: Tools > Options > Documents > Detect when a file is changed outside the environment

For VS2010/2012/2013/2015: Tools > Options > Environment > Documents > Detect when a file is changed outside the environment

Upvotes: 54

Drew Noakes
Drew Noakes

Reputation: 310907

Because a picture paints a thousand words...

enter image description here

Upvotes: 9

Brad
Brad

Reputation: 111

In Visual Studio Pro 2012

There is an "Auto-Load changes, if saved" that works.

Tools > Options > Environment > Documents > Detect when a file is changed > Auto-Load changes, if saved

Upvotes: 11

dan-gph
dan-gph

Reputation: 16909

I generate source files on every build, and I don't (normally) get a "file has been modified" message if the file is not open in the editor.

I was getting it just now, however, on a closed file. (That's why I went searching for this question.)

I think that's a bug. The file seems to get wedged sometimes. (But this is the first time it has happened in about a year.)

I think I've found a work-around just now: Open the offending file and then close it again.

The point is, you shouldn't need to turn off changed file detection.

Upvotes: 4

Related Questions