An error occurred. Detailed message: Failed to inflate packfile This error has been reported and supposed to have been fixed. I am using VS2013.5.5 and the error is still present. https://connect.microsoft.com/VisualStudio/feedback/details/817701/libgit2-error-trying-to-checkout-clone-a-git-repository-to-network-path-with-visual-studio-tools-for-git
slow, buggy, does some crazy disk i/o that slows down my entire computer, ** in ignore doesnt work, vs get hung in this git2-msvstfs.dll!_git_graph_ahead_behind method for over 10 minutes sometimes at startup, visual studio stays running even after close now and it causes visual studio to lock up all the time. I get these weird cannot stat file errors where I need to go and physical delete a file in bin folder generated by the build. Also the Add icon looks almost exactly the same as the unmodified icon. Wouldnt recommend.
Yesterday after working for couple hours taskman showed 100s of gbs of read i/o. The issue resolved it self after I deleted a file in test results folder that was locked by sql server. After that I tried to open another solution, after waiting five minutes I just gave up and uninstalled.
I switched to the 3rd party "Git Source Control Provider" with tortoisegit. So it is great, no issues perf issues. Probably wont be checkin anything until monday so will know more by then. All I need is add files and commit in stable way, everything else I do from command line. So if it does that without perf issues then its a 5/5 for me.
Very, very unstable for me. I constantly have issues committing due to odd 'File In Use' errors, the plugin constantly doesn't add files to git that I've added to my projects and so missed commits happen frequently. Just not ready for prime time.
I've been trying hard to use this thing shortly and already going furious.
-no stash support -no rebase support -no interactive rebase support -files with unconfirmed merge conflict resolution are presented as Pending Removal
This tool albeit having Git in name actually promotes quite the opposite, central fashioned methodology and effectively discourages practises invented and intended for distributed systems like Git. I mean, really?
I like the conflict resolution view.
Apparently the only viable way of collaborating and keeping working copy refreshed by other contributors is to: 1. Commit (or revert) unfinished changes before pulling from upstream. Commit for the sake of commit. Reminder: no stash. 2. Pollute history with unorganized heaps of commits. Reminder: no stash, no rebase, no interactive rebase. 3. Delegate unsupported but mission critical operations to other tools. Why not stay with them and avoid VS Git placeholder in the first place then?
The way this tool is integrated in VS and what capabilities it exposes (or better hides) is a total bummer and discourtesy to any self respecting Git user. On the bright side: 9/10 masochists disagree.
It's ok, but nested .gitignore files are not properly considered (or overriding properly). The Git GUI shell extension for Windows works perfectly fine with my .gitignore files, but nested ones are not handled properly by this VS extension, and files that should be hidden using wildcards are still showing. For example, in one .gitignore file (in a parent folder) I have: /Source/*/*.js /Source/*/*.min.js /Source/*/*.js /Source/*/*.map **/DSJS/*.js **/DSJS/*.map **/DSJS/*.min.* **/DSJS/*.txt And in another .gitignore in a the sub-folder (/Source/DSJS/) I have: /*.js /*.map /*.min.* And all these files types still show.
This is really helpful for working with Git in Visual Studio.
I would like to be able to use an external diff / merge tool (Beyond Compare). I got really used to that when using TFS. Unlike command line git, this extension seems to ignore the diff.tool and merge.tool settings in .gitconfig.
I would like to request that you either use those settings or add an option in the Tools/Options/Source Control/Configure User Tools menu a la TFS?
Im working on a project from 2 different computers. Both have the same version of Visual Studio 2013.
If I work the home computer, commit, push, go to my other computer - have no pending changes or unsynced commits, try to pull/sync - I get "An error occurred. Detailed message: 3 conflicts prevent checkout", everytime.
If I fire up the command prompt and do a "git pull", no conflicts and it pulls just fine.
A quick fix or anything for this? Very annoying to not be able to use the tool in VS and have to rely on the command prompt just to get new commits.
Open with 7-zip
<Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" Version="4.5" />
<Dependency Id="Microsoft.Framework.NDP" DisplayName="Microsoft .NET Framework" MinVersion="4.5" />
An error occurred. Detailed message: An error was raised by libgit2. Category = Net (Error).
I am encountering this error while cloning operation, within visual studio 2012. Using Git BASH or Git GUI, I am not getting any error and successfully able to clone remote repository. However, having issues in pushing local changes back to remotely(using GIt BASH) - getting error as 'Cannot access URL http://mygitserver.com/gitrepo return code 22'
Git server is on Ubuntu 14.04 linux and git client is on Windows 8.1
Could anyone help me to resolve these issues.
Really appreciate for the help !!
I get the following error when trying to push to bitbucket (it has pushed successfully previously, many times):
An error was raised by libgit2. Category = Net (Error).
Chunked encoding upload is not supported on the HTTP/1.0 protocol.
When someone changed *.csproj or add files through Visual Studio extensions, the Visual Studio Tools for Git will not add these files into Tracked file so all these files will not commit automatically. It must be include these files manually in order to commit to the repository. Is it a bug? Or is there anyway to fix that?
I am getting the following error.
ystem.IO.FileNotFoundException: Package 'SccProviderPackage' failed to load.
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
at Microsoft.TeamFoundation.Git.Provider.ServiceProviderExtensionMethods.EnsurePackageLoaded(IServiceProvider serviceProvider, Guid packageGuid)
at Microsoft.TeamFoundation.Git.Provider.ServiceProviderExtensionMethods.EnsureSccAndTfPackagesLoaded(IServiceProvider serviceProvider)
at Microsoft.TeamFoundation.Git.Provider.Settings.SettingsLinksSectionVS.Initialize(Object sender, SectionInitializeEventArgs e)
at Microsoft.TeamFoundation.Controls.WPF.TeamExplorer.Framework.TeamExplorerSectionHost.Initialize(Object context)
This is not installable on the resulting version of visual studio from a SSDT/SSDT-BI install, so it appears that git cannot currently be used for SQL Server development when a full blown version of visual studio is not also installed. Seems rather strange that express products are supported when SQL Server developers are not.
Connect bug is here:
We use git with TFS but we didn't see the our avatar pictures on the different windows except the picture of one college. We have check and we have a picture in the TFS online portal. We use TFS integrated with the active repository.
First: I like Microsoft Git Provider
Maximilian added this issue:
And I agree with him. If you say that a certain file should not be included in source-control by adding it to .gitignore it should be respected. If a developer adds that file or if you have build targets that does it (automatically) it will still show up in the "Included Changes" list, even if it is excluded through .gitignore. I found it very confusing. Git does not behave that way and "Git Sourece Control Provider" does not behave that way but "Microsoft Git Provider" does. The consequence will be that files will be added to source-control by mistake because you forget to exclude them.
If this is not the right place to report this kind of issue, please tell me where to do it.
I am in agreement with Hans/Maximillian, the gitignore issue not respecting what we have set to be ignored causes a lot of conflicts in our dev team. So much so that they are wanting to throw out Git. Please correct this issue as it is not the way Git was intended to work. Thanks.
Any resolution on this issue? I see the official bug listed as closed, fixed in Update 2. I am currently using VS 2013 Update 3 and still experiencing the bug. Has Update 2 resolved the bug for you? Have you tried Update 3?
I'm hitting the same issue. 10 year old project imported into VS2012. Added to source control via Solution Explorer context menu. .ignore file modified with latest from github for VS. When committing, ALL files get committed! As if .gitignore didn't exist. This is a bug that needs fixing ASAP. When can we expect it?
Here is a post with an answer that worked for me. In case the link is broken, the answer from Eric Nelson is :
Close Visual Studio.
Navigate to your .git folder
Restart Visual Studio