Git changes not showing in VS2013 Update 2

Question

I am using Git in VS2013 and my changed files are not showing up in the Changes window of VS.

When I have changed a file but before I have saved it to disk it does show

Answer 1

Simple solution:

1) Close VS 2013 and manually rename the solution's folder. 2) Reopen VS 2013. VS will prompt you to clone the solution from the server in order to open it. Follow the prompts and clone a new copy of the solution. 3) Close VS 2013 and use Beyond Compare (or some other file compare system) to manually move your changes from the old solution to the new solution. 4) Reopen VS 2013. Your changes will show up and you can commit them to the local and remote repository.

---More information---

Had the same problem. Made a change to a file in VS 2013 Update 4. Before saving the file, the changed showed in the "changes" screen (and a check mark appeared next to the item in the solution explorer). After saving, the item no longer appeared in the "Changes" screen (and the icon in solution explorer changed back to a lock).

This issue may have occurred due to one of the two recent changes I made to the project although I haven't had time to attempt to reproduce the scenario.

1) I manually (outside of VS) did some copying/backups to deploy a new version of a third party js lib. original folder structure: c:\git\solution\webProj\scripts\jwplayer\premium\jwplayer.js c:\git\solution\webProj\scripts\jwplayer\free\jwplayer.js

new folder structure: c:\git\solution\webProj\scripts\jwplayer\ c:\git\solution\webProj\scripts\jwplayer\jwplayer-6.11__MACOSX c:\git\solution\webProj\scripts\jwplayer\jwplayer-6.11\jwplayer c:\git\solution\webProj\scripts\jwplayer\jwplayerOriginal\

This was an attempt to isolate the jwplayer.js (and other required files) into the jwplayer directory. The new __MACOS directory had filenames starting with a ".". There's a theory that the path to those files could be throwing and error during VS 2013's processing of changes.

2) I had recently gotten nuget updates. Caveat, prior to the nuget update, I had removed the reference to the .map files in the base js files under the scripts directory (long bad story). When I tried to update from nuget, nuget recognized the changes and failed the update, but still updated web.config and packages. This resulted in a mismatch between what nuget thought was installed and what was actually installed. I used the VS 2013/git integration to "undo" each of the updates, but may have missed something.