Pending Changes across projects seen in Visual Studio - visual-studio-2010

Is there a VS setting that limits the pending changes I see to those of the current project? I have VS 2010 and when I attempt to view all pending changes, the list includes changes from other solutions.

There is a button in the button bar of the "Pending Changes" window that limits the listed changes to the current solution. Be careful using this, though, because sometimes there is stuff that probably belongs in source control but isn't actually part of the solution.

Related

How can I show all changes at once?

Is it possible to view all the changes at once without having to click each time each file?
I would like to have a view like a Pull Request view where you can see all the changes scrolling down.
Visual Studio 2019
No, a scrollable page view of changes is only provided in the web version. In Visual Studio in the Teams -> Changes section it shows the changed files, but one has to click-through them to see the difference.

Visual Studio 2013: auto-refresh solution explorer in "show all files" mode

Is there any way or some unobvious workaround to make the Solution Explorer refresh automatically (in Show All Files mode) when there are changes to the project directory tree? Currently if I rebuild a project with different output settings (which would add some files and remove some others), no changes would get reflected in Solution Explorer until I manually click refresh button. Doesn't seem too convenient for a tool aimed at programming, i.e. automating repetitive tasks...
Update
A picture is worth a thousand words:
My relevant options # Tools > Options > Environment > Documents:
Let's assume that Release directory is empty and Show All Files mode enabled
Now, I build my Release config... Build succeeds, but no changes are visible in Solution Explorer:
Only after I hit refresh button manually can I see the results of build process:
So I'm basically asking if there are ways to make Solution Explorer update automatically when changes occur, not to make externally modified files auto-reload in VS editors.
#Sunny Moon - There is no option right now to automatically refresh the project tree if changes are introduced. You have to manually select the Refresh button in the command bar of Solution Explorer. I'm going to track this feedback along with other areas I've been collecting for Solution Explorer so thanks for sharing your frustration here.
Thanks!
Cathy
Visual Studio IDE Team
Just set check the “Auto-load changes, if saved” check box on VS2013 Option menu >> Environment menu.
That was impossible in VS 2013 and 2015, but with 2017 Microsoft did the right thing and revamped the Solution Explorer a bit - now there is clear and logical separation between solution (virtual) and folder (physical) views, and changes to the filesystem are now tracked and displayed automatically.

I want "track changes" in Visual Studio to show changes that have not been commited to version control

"Track changes" in Visual Studio shows what lines have been edited in the current session (shown next to the scroll bar). But to me it is much more meaningful to see what lines have changed from the last version in version control.
In Eclipse this is possible. Is it possible to have the same in Visual Studio? I am using VisualHg, and Mercurial, but I suppose the same principle should apply for other version control solutions.
I suppose you want to see the changes next to the scroll bar such as the track changes.
I don't know how to achieve that. But I use TortoiseSVN and have an addon for VS (ankhSVN is the name, I guess), which lets me do a right click on the file and do show changes. There pretty sure is an equivalent addon for mercurial.
Maybe an addon such as Power Tools or VS Commands may provide a way of marking the lines you've changed next to the scroll bar.

Visual Studio 2012 project lost link to TFS

So I came back to a project that I was working on a few months ago, and when I load it one of the projects seems to have lost the link to it's entry in TFS. The solution explorer doesn't show the lock icons for it, but I still see it in TFS.
I tried performing a add to source control but it says that the items already exist.
Anybody have ideas on how to fix this?
I'm trying to avoid remapping because there are a few branches, and I'm not even sure that will fix it.
Your solution has lost the TFS binding, you can do the following to fix it. First open the solution/project you wish to bind in Visual studio then:
Highlight the project or solution you wish to bind to Team Foundation version control in Solution Explorer.
On the File menu, click Source Control, and then click Change Source Control.
3.In Change Source Control dialog box, click Bind.
MSDN Link
Update for VS 2013 (thank you Caad9) - In VS 2013 [Ultimate at least] there's an additional level in the menu; File - Source Control - Advanced - Change Source Control... which brings up the dialog

Stop Visual studio Auto-selecting files in Pending Changes after checkin with TFS

I use the Pending Changes window in Visual Studio 2010 to manage my files and to checkin with TFS.
My problem is that I will often be working on something and have files checked out then go onto something else, and then something else etc.... I have a lot of files checked out at once.
When I do a checkin, even if its just 1 file visual studio automatically checks the checkbox next to all other files so I have to go through and uncheck the files I dont want for my next checkin.
Is there any way to turn this feature off?
Thanks
I don't think you can turn of this feature. To better control this behaviour you have a few options:
Select the folder in which you have the files that you want to check-in and right-click for the menu and choose from there for Check-in pending changes. That will select only the files within the folder/subfolders or project that you selected from the solution explorer.
You can use a trick to deselect all files marked for check-in in the pending changes window, by selecting one file, press CTRL-A and deselect a file.
Hope that these tips will give you a smoother check-in experience. Also take a note at the comment by Lars Truijens about not mixing changes. It will be very hard to separate these checkins at not break the build at some time.

Resources