![]() ![]() ![]() I closed and reopened VS, and cleaned and rebuilt the solution, more than once. ![]() I have been making changes in a local development branch, but couldn't see how my single local commit could be causing the weirdness-I just hadn't made those kind of changes. Discarding the modified file (on the theory that I wanted the changes added in the most recent commit from upstream) did not help. I couldn't build the solution due to this file having been modified and the solution not being aware of important new dependencies (references added to two projects). sln file but my changes shouldn't have affected the project). (That is, git status showed a new modified. It seemed like Visual Studio was doing it, but I don't know for sure. While coding in a local branch, a Visual Studio solution file kept appearing to be modified without my intervention-its new contents exactly undoing just one file in the most recent commit (but not undoing the other 3. Symptoms in the best order I can remember: I ran into a situation today where, after pulling from an upstream branch and rebasing, recent commits to the upstream branch were acting like they hadn't taken effect.
0 Comments
Leave a Reply. |