CODEWITHSUNDEEP
c#visual-studio-2012visual-studio-2013
Jonathan Beerhalter
Jonathan Beerhalter

Reputation: 7407

What causes Visual Studio to reload projects?

Our team has a solution that has 15 projects that we all work on collaboratively using git for source control. Sometimes when switching branches Visual Studio simply updates the source files and the branch switch takes seconds(bounded by how fast I can type commands).

Other times though, when switching branches, Visual Studio will popup a dialog saying that it needs to reload all the projects and then I have to sit and wait for approximately five minutes while Visual Studio goes through this process.

I'm guessing that something we're doing with line endings is causing us to touch one of the Visual Studio specific files, and that causes the reload, only I'm not sure which one, or if that's even the right path to go down.

So my specific question then is, "What causes Visual Studio to need to reload projects?"

Upvotes: 4

Views: 757

Answers (1)

Patrick Hofman
Patrick Hofman

Reputation: 156948

In fact it is quite easy:

Every file change will cause Visual Studio to reload the file, whether it has really changed, or not.

When changing a project file, it will reload the entire project.

Maybe git, or some other software, is updating some attributes of the file (so not the content). This might trigger the 'Visual Studio' file change monitor already. I have the same issue using TortoiseSVN.

Upvotes: 5

Related Questions