Microsoft GIT strikes again

Wanted to test a new wcf service that I have to integrate with, so started off with a blank console app.

Go to visual studio and select add service reference, etc, and then once all done hit ok.

Only to be presented with this

msgit1

Unable to check out the current file. The file may be read-only or locked, or you may need to check the file out manually.

and then this

msgit2

The operation could not be completed.

Turn out the problem is that for Visual Studio’s Source Control it was set to “Microsoft Git Provider” as the current source control plug-in

Why oh why does this plug-in think that Git is like SourceSafe where you have to physically check out every file before you can do anything.

I know its my own fault I should have ensured that my source control plug-in is set to None but why can Microsoft not get its head out of SourceSafe mode.

Advertisement
About

My musing about anything and everything

Tagged with: , , ,
Posted in Git, Source Control Plug-In, Visual Studio

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 13 other subscribers
%d bloggers like this: