Me and my colleague are working on a project and I wanted to pull the SSIS packages from colleague's repo into my local repo. I did the git pull origin colleaguerepo
to pull from the remote and I am able to see all the files when I type in 'ls' . But when I open it in the Visual studio the files are missing. there were no error messages shown or any merge conflicts too.Could anyone help me on this matter?
Here are the summary of what I have done.
colleague pushed the local repo to remote.
I did 'git pull origin colleaguerepo'.
'ls 'in git shows all the files.
but visual studio does not show it.
Upon opening my ASP.NET Core project with an existing git repo in Visual Studio 2022, the git repo is not being loaded. However, opening a freshly cloned repo of this project from GitHub works fine. And opening other projects with git repos work fine. What could be the issue?
Had the same issue after upgrading to latest version of VS2019 and had a look at the output from "Source Control - Git", there were messages of a fatal error because of no access and suggesting running the following:
git config --global --add safe.directory path/to/repo
After running it and restarting VS2019 it works OK.
Had the same problem running VS2022 under Win10.
Problem was that the ownership of the file system directory containing the solution and git data had changed to Administrator. After changing the ownership back to my normal windows user account everything worked fine again.
If you run VS 2022 as an Administrator, it should load everything as it should.
In my case the project was cloned in console with Administrator rights. All worked good in console but Visual Studio was not read the .git folder.
Actually folders has enough rights for Authenticated Users group that was assigned for all child objects but Visual Studio still not see .git folder.
Only after change owner of project folder and all child objects to current account Visual Studio seen .git
Steps:
Open Properties of project folder.
On tab Security select button Advanced.
Select tab Owner and button Change.
In List select your account plus check "Replace owner on subcontainers and objects".
Click Apply
I ran into the same problem.
Visual Studio Code and Git bash correctly recognized the repo but not Visual Studio 2022.
I installed the latest version of Git in the system, and the visual studio recognized the git repo correctly.
I have installed Tortoise SVN and used it once or twice but I set it up incorrectly and would like to do a full wipe and reinstall. I do also have the Visual SVN plugin installed in Visual studio. This includes deleting any repositories that I have created. I tried deleting and reinstalling everything including my Repository, and reinstalling the Visual SVN, but now I cant create a new repository on visual SVN in the same location because it says that it already exists?
Try going to the folder and showing hidden files, there should be a .svn folder there. If you delete that, it should solve your issue. – Nanos Apr 4 '18 at 17:44
#Nanos's Comment is what I was looking for.
I'm not getting something about Visual Studio's Git for TFS.
I cloned a colleague's solution in Git on TFS and started adding code. I then realised that I needed my own branch for the changes I was making, and so following the instructions in Push a new local branch to a remote Git repo and track it too I ran
git checkout -b e4ctim
git push -u origin e4ctim
When I make changes to my code visual studio shows the familiar red-tick icon by the code file to reassure me that the change has triggered the file to be checked out:
And then when I save the file the Visual Studio returns the icon to the blue padlock. I assume that this change from red-tick to blue padlock signifies that the change has been checked-in locally in Git:
But when I look at the history of the modified file, there is none!
I would like to commit my changes locally and sync them with the TFS server.
Visual Studio does not see any changes at all:
From the command line I can see that Git has noticed all of my modifications by running the command
git status
and seeing lots of changes not staged for commit and untracked files.
Looing at the Git book I could use
git add
or more specifically
git add -u .
to stage the files ready for a commit but I'm reluctant to do that as the Develop your app in a Git repository (track, commit) Visual Studio documentation states:
Q: Where is the Git stage?
A: If you are an experienced Git user, you might have noticed that
Visual Studio handles changes differently than the command prompt.
You might have wondered if the Included Changes section contains
your staged changes. In fact, Visual Studio usually bypasses the Git
stage for you. When you commit changes, Visual Studio simultaneously
stages and commits them. The one exception occurs when you add a
file to your Git repository; Visual Studio does stage this kind of
change.
Visual Studio stages and commits changes simultaneously. But why is it not listing any of the modifications I have made to tracked files as changes, and thus letting me commit them?
This is more of a workaround than an explanation, but I found that if I ignored the documentation "when you commit changes, Visual Studio simultaneously stages and commits them" and instead added the modifications to staging with the command
git add -u .
then Visual Studio suddenly became aware of the modifications and let me commit them locally and sync them with the TFS server. Moreover it then put the 'new file' green cross on the files I had added and I found I could do another commit and then another sync to pick up the additions and deletions I had made.
Since then Visual Studio is doing what I would expect: when I make a change to the file the file is listed as changed in the commit window.
I still do not know why Visual Studio failed to pick up the changes until after an initial git add but at least it works now.
I had to add this line to my .gitignore:
[path to project]/node_modules/
Apparently VS2015 was crashing on some very long path in there and would just decide to give up all hope
delete the file myProject\.git\index.lock fixed it in my case.
I had the same probem and I realized the following:
In order to show the changeset, As #dumbledad said, Visual Studio runs the command
git add -u
internally for staging the updates.
If some of the files that you are trying to add to your changeset is open by another process, then the git command gets a permission error. And Visual Studio won't show the changes.
In my case, I had a document in my repo that was open by another application, and that caused Visual Studio not to show the modifications because of the Git permission error. So check if any of the files of your git repository is not open by any other application.
I'm using VS 2015 Update 1 and also meet this problem. Furthermore, at the same time, the VS' output window told me my VC.opendb file under the solution folder is occupied by another program. According to this, I fixed the issue of occupying: add *.VC.opendb and *.VC.db to the .gitignore file. Then everything goes well.
I was having the same issue with Visual Studio Update 3. VS was saving locally but not picking up any changes so I couldn't commit.
I downloaded Git for Windows from https://git-for-windows.github.io/ (thanks #fhilton), opened the Developer Command Prompt and changed directory to C:\Repos\Scheduler (the location of my source code).
I then ran GET ADD -U and received the following error...
error: open("WindowsServices\Scheduler.WindowServices.InstallLog"):
Permission Denied
error: unable to index file
WindowsServices\Scheduler.WindowServices.InstallLog
fatal: updating files failed
As others have said, it looks like the GIT tools in Visual Studio can fail silently, even for the most basic Windows level errors. Worse, it can tell you GIT is fully in sync. Command line is certainly your friend for the time being.
Open View > Output, select 'Source Control - Git' in Show Output from and check for any errors. As others mentioned, any error in Git makes MS Project silently ignore any changes.
I had this problem on a new machine with a fresh install of both VS2013 Update 5 and VS 2015 and it was driving me crazy. Then I found if I installed Git for Windows, the problem went away! https://git-for-windows.github.io/
Then i was trying to make changes but files doesn't get effected...There is a easy solution for this. The major problem is one of your git ignore files ignoring your files..
Open your local repo for instance D://repos, then look file you want
--> D://repos/project1/HomeViewModel.cs
--> Right click on it and click on Git Extentions
--> Choose +Add Files
--> then Force option
--> Click on Addfiles..Here you go you file will be added in changes
Helpful article! Using Git Bash (git add -u) helped me get closer to the cause of the problem. After committing changes previously not shown in Visual Studio, only half-way commit was done because of using a SQL Server Database Project; Apparently, Windows 10 started to add jfm-files in the same folder keeping it open all the time and preventing it from beeing accessed by VS. Solution was to add it to the .gitignore before committing.
See this thread for further information:
Visual Studio 2015 Database Project directory contains a file with extension jfm
In my case my problem was I am using Linux with symbolic links in the path to my projec (cannot tell if windows with symbolic links has the same problem)
We are using SVN repository. Please note this is the 1st time I am using it and I have used TFS before.
To get latest code from SVN we do a checkout on the project folder.
After that there is a green checkmark on the locally downloaded folder.
When we try to open a visual studio solution from this folder, we get error loading project due to SVN references. Is there anyway to release the SVN checkout lock or something?
I have resolved this by deleting the SVN reference lines from the Project file by opening it in notepad