I cannot seem to unlock the Unpushed Commits indicator to quickly view how many commits I have made. This is however not necessary when you regularly push, though I like to keep some projects locally.
Here is an example:
The same applies for the indicator next to it, which is the change indicator.
I looked in the git settings, though no such option seems to exist.
Currently using Visual Studio 2017RC, any suggestions?
I got the same issue as yours in my VS2017 RC, but if you put the mouse on it, it would share the correct value:
My suggestion is that you'd better edit your project files together, and then commit them with few times. Or just put the mouse on the "99*", and view the real items.
Of course, since it is the RC version, I also help you submitted a feedback to the product team here:
https://developercommunity.visualstudio.com/content/problem/15796/visual-studio-unpushed-git-commits-indicator-limit.html
You could vote and add your comment there:)
Related
My team uses TFS 2013/Visual Studio 2013 to do code reviews. It all works fine but there is a really annoying thing which VS does that I can't seem to turn off.
If I submit a review and it comes back with suggested changes, I go through and make them, checking each one off as I go. The problem is each time I mark a code review item as done by checking the box to the far right of it in the Team Explorer -> Code Review view, VS opens the diff window for that particular item showing the review comments. I don't want to see any of that, I just want to mark the item as done so I know I've dealt with it.
Is there any way to prevent VS from showing the diff window when you mark a code review item as done?
I'm using Visual Studio 2010 and AnkhSvn. There's a panel called PendingChanges (it's main panel). I use it to switch to different branches. There is a combo-box with path to current branch and "Other..." entry. I think when I switch to different branch it supposed to remember path to previously loaded branch so I can quickly switch back. But it doesn't. Am I doing something wrong? Or maybe there is a setting to do that? Is there a quick way to switch between different branches?
P.S. Don't know whether this question is for SO. If not, delete please.
You're not doing anything wrong. The drop down doesn't show recent branches (yet).
How do people generally deal with TFS when you've got to work with multiple solution files? If you've got one instance it's easy because you can always go to that window for the source control explorer, pending changes, check on builds or work items. But when you have 4-5 solutions, it becomes tricky to deal with. You might expand some folders or check some pending items on one VS instance but you have to remember which one you did it on.
Having a separate instance dedicated just to TFS tasks is tempting, but there's only one window state for the whole program. If that instance is closed last, all instances will come up with all the TFS windows open.
How do other people deal with this? Can you use separate profiles somehow and cordon off a "TFS" instance of Visual Studio?
Use the Pending Changes window. View -> Other Windows -> Pending Changes. This has a toolbar option to show only those changes pending for the current solution also. It's the last toolbar button in the Pending Changes window. I usually make this a full document in VS and then memorize the keyboard shortcut to it: ALT+V, E, H. Obviously you could bind your own shortcut, but what fun is that.
Eclipse has a similar perspective/view to Pending Changes, but it's name escapes me and I don't have my Ubuntu VM up at the moment.
Solution Explorer and Source Control Explorer are definitely not my recommendation for check-in activities. I personally like to clear out all of the checkboxes on Pending Changes and then Diff each file. This keeps me from A) waiting too long before a checkin (it sucks to compare 20 files 1 by 1) and B) avoids checking in a change I didn't intend.
If you have multiple instances of Visual Studio open at one time (which I'm not quite sure why you would need to do this), your changes are "synchronized" across all instances of Visual Studio. Don't do your check-in from the solution explorer, do it from the Source Control explorer, then you're sure to get all your updates in a single check-in.
You might find VSCommands useful when working with VS/TFS - it can be configured to display the Solution and TFS Branch name in the title bar, this indication is invaluable when working with multiple instances of VS (or multiple branches of the same project).
I recently switched from a Java based project to a C#/.net project. I previously used IntelliJ which had the concept of change lists where you could group your pending changes together and check each group in individually.
I have two problems with the pending changes window in visual studio.
1) Every time I check anything in, visual studio checks the checkbox beside Every pending change in the list forcing me to uncheck each and every one of them so I don't accidentally check something in. This is extremely frustrating because there are several files that I need to keep changed to correctly run my code locally. Is there any way to change this default behavior to not check any pending changes on check-in?
2) Is there any way to group changes into lists as opposed one big bucket of changes? Again this becomes frustrating when I need to check something in, but I have to search through the files and check the pertinent changes. I understand that shelve sets exist using TFS, but that doesn't cut it for me, especially since I have several changed files that I need to keep altered in order to correctly deploy locally, and I rarely ever want to check in.
Thanks in advance!
I have to manage lots of changes every day in Visual Studio, and I've got a few tips for you, but no silver bullet:
Use Ctrl+A to select all items and then press a checkbox to toggle the checkboxes for all items. This can be useful when performing changes to only a few items -- just uncheck everything, then make sure you have only the items checked that you'd like to update.
Use Ctrl+Click (then right-click) to 'Undo' selected changes. By default, the undo action will only apply to the selected items.
You might want to experiment with using multiple Workspaces -- and then filtering changes by workspace or by solution.
No, I don't know of a way to fix your problems. It sounds like the best answer would be to refactor your configuration settings or code so that you can check in all of your changes.
If your changes are in different projects you can partition what you check in using the Source Control Explorer by right clicking on the project folder and checking in that way. It will auto check only the files in the folder you right click on. Just keep in mind the Source Control Explorer gives you some other options. Otherwise, I do not know of a way to manually control your change sets file-by-file thought if this exists I would like to know about it too.
You can also use Ctrl+A to select all items and then press Spacebar to toggle the checkedboxes as checked/unchecked.
Just installed AnkhSVN and I see the equivalent of "svn up" but I'd prefer to run "svn st" first so that I don't just blindly update.
The next release of AnkhSVN will enable the 'Recent Changes' tab in the pending changes window. This allows the equivalent of 'svn st -u' (It shows outgoing and incoming changes).
We are still working on the usability of this view in the
daily builds.
Input welcome on the AnkhSVN users list.
There's a pending changes window you can add that will show what files you have changed in your local working copy. I usually keep it in the set of docked windows where the output window is. In general, you can also tell what status a file is in by the icon next to the file. For example, a plus sign means that it's been added.
UPDATE: Here's a guide to the icon overlays. They should be about the same as in Tortoise SVN.