I did this, making sure that the path to the **git-lfs.exe** (C:Program FilesGit LFS) was in my path, but I still had the problem.ġ1 12 This is where I got stuck and hence needed to get some help from the Microsoft Visual Studio support team.ġ3 14 After a good deal tracing they spotted the problem. bin file I got an error ‘git-lfs filter-process: gif-lfs: command not found’ĩ 10 On reading around this error it suggested that the separate () needed to be installed. So I was able to enable LFS support on a repoģ 4 and manage standard and large (.bin) files without any problemsĥ 6 However, when I tried to make use of this cloned LFS enabled repo from inside Visual Studio by staging a new large. The big problem I had was with LFS, which is meant to work in Visual Studio since 2015.2.Īgain from the command line operations were seamless, I just installed Git 2.16.2 via Chocolaty and got LFS support without installing anything else. There is a request on UserVoice to add these functions to Visual Studio, vote for it if you think it is important, I have. This is unlike the Git command line, which allows actions to span a parent and child repo with a single command, Git just works it out if you pass the right parameters At this time you can clone a repo that has submodules, but you cannot manage the relationships between repos or commit to a submodule from inside Visual Studio.
#GIT LFS WINDOWS TRIAL#
However when I tried accessing my trial repos using Visual Studio 2017 I saw issues Submodulesįirstly there are known limitations with Git submodules in Visual Studio Team Explorer.
#GIT LFS WINDOWS CODE#
So as part of this migration and re-structuring I am looking at using Git Submodules and Git Large File System (LFS) to help divide the monolithic code base into front-end, back-end and shared service modules using LFS to manage large media files used in integration test cases.įrom the PowerShell command prompt, using Git 2.16.2, all my trials were successful, I could achieve what I wanted.
TFVC and Git are just too different in the way they work to make history migrations worth the effort in my opinion. Obviously, I have ruled out anything that tries to migrate history as ‘that way hell lies’ if people need to see history they will be able to look at the archived TFVC instance. There are a number of ways I could do this, as I have posted about before. I am currently looking at the best way to migrate a large legacy codebase from TFVC to Git.
0 kommentar(er)
