Ah, so that is why Git isn't reacting- VS has the file in memory but
doesn't lock it, then overwrites git's changes with whimsical abandon?
How unhelpful.
On Tuesday, October 30, 2012 6:35:53 PM UTC, charlesmanning wrote:
>
> I don't think VS is locking the files. Instead, VS has the file open
I don't think VS is locking the files. Instead, VS has the file open
and will write back to the file as you do things.
Depending on how VS does this, file contents can get confused.
Some of this problem must be blamed on the stupid way VS manages
projects. It would be sane so separate build and pr
Sometimes if I have a solution open in Visual Studio when I pull from Git (
a common situation in this type of development environment ) it seems that
Visual Studio will have certain files locked so that Git fails to overwrite
them.
When that happens Git doesn't seem to care- it continues the
