I recently installed Visual Studio 2013, and I’ve noticed the Pending-Changes screen no longer informs me that “The files are identical” when appropriate.
I often have a list of files displayed in my Pending-Changes screen. Some of those files have been unnecessarily checked-out by me, so I try to clean-up my list daily. In Visual Studio 2010, I can right-click on a file in Pending Changes, and click Compare > With Latest Version. When my local version matches the Latest Version, I get a notification saying, “The files are identical”.
However, in VS2013, when I compare a local file w/ Latest, the file-comparison window opens and displays two identical files side-by-side with no changes highlighted (because there ARE no changes to highlight). Is this an option/feature I can change in VS2013?
It's a change in behavior in VS 2013. I'd suggest entering it on Connect.
Related
I'm trying to compare two versions of a VBA file which are placed on a TFS. The Diff Tool shows several changes, but there actually are none.
♪And they don't stop coming...
In fact, VS tries to beautify the code by changing it's case despite the fact that I turned the Pretty Listing feature off.
Example
Well, I've disabled literally EVERYTHING here
Note: VS does not change the files either on disk or TFS.
The question is how to make it stop. I can't find real changes when comparing files.
Microsoft Visual Studio Community 2019
Version 16.4.6
I've recently noticed that when I go to make a change which needs a file to be changed, VS2017 (Professional) has started to produce a popup saying:
The file <filename>, which you attempted to edit, is read-only on disk.
Would you like to make the file writeable or edit it anyway?
If I cancel this, I get a message:
The file '<filename>' needs to be checked out before it can be edited.
The file was not checked out automatically because you have disabled automatic checkout
when files are edited in the Source Control options page.
The Source_Control->Plug-in_Selection is set to Visual Studio Team Foundation Server; I haven't changed the Options under Source_Control->Environment; both Saving and Editing are set to Check out automatically.
As far as I know, apart from recently updating from 15.7.4 to 15.7.5, I haven't changed any settings. Is there some setting elsewhere which affects this?
Note, my installation of VS2017 Pro Preview, 15.8.0 preview 5.0, does the same thing and running VS2017 as Administrator does not fix it.
Update:
Visual Studio 2015 has no problem checking out the same files in the same local workspace. That is, if I open a solution in VS2017, edit a file and go to save it, I get the above messages. If I then cancel the edits and try the same thing on the same file in VS2015, the file gets checked out. Hence the problem is with VS2017 and not the files themselves.
OK. After further searching I found a pointer to the answer in this answer. Somehow, my VS2017 instances have gone offline from the TFS server. The menu option File->Source_Control->Advanced->Go_Online sorted things out.
My solution had become unbound from the source control server.
To resolve I used menu options File->Source Control->Advanced->Change source control... Select project or solution without Server Name or Server Binding. Click Bind.
I'm using VS 2010. I've just made changes to a large number of files in a project. About 40 or so files got deleted. I checked out the entire project first (using Team Foundation 2012 as our source control). Now when trying to check in, I see an error "Could not find file 'C:\folder\filename.dll'" in a popup dialog. This is the first missing file it came across. When I check the Output window, I only see that one file. I know there are several others.
Visual Studio 2012 will display the list of all of the missing files in the Output window.
Is there a way to do this in VS 2010?
There is no way to do this in Team Explorer 2010. Due to feedback this behaviour was changed in Visual Studio 2012.
Note: Visual Studio 2010 drops out of mainstream support in July.
I would try command line first, tf checkin, posdibly with /i (not to prompt) and /validate (to not risk actual checkin).
Other, very basic solution is to get list of all checked out files(tf status) and write a script that undo checkout if file does not exist.
I have VS 2008, 2010, and 2012 installed.
Initially, VS2013 Team Explorer was installed (Shell only). I uninstalled that.
Now, the Visual Studio Version Selector shows an empty list when executing a .sln file. Nothing shows.
How can I repopulate this list? Where is it stored? Registry? I tried to find entries, but since it doesn't actually have any items in the list, I couldn't search for a specific string.
I just encountered the same issue after installing Visual Studio 2015 parallel to an existing 2013 installation. In my case it turned out that that the problem was related to the solution file itself: It seems that the version selector does not like BOMs etc. (don't know how the solution got crippled, though). Make sure that the solution starts with
Microsoft Visual Studio Solution File, Format Version 12.00
and has no space, non-printable character etc. before that. After saving the file, the effect should be immediately visible with the correct icon returning.
I just ran into a similar problem where this dialog started popping up after a recent Windows Update (Win10) on 1/6/2018. That update caused all sorts of havoc in terms of broken file associations.
I tried searching for solutions and trying a few things but everything was overly complicated and messy.
My solution was to run the Visual Studio (2013) repair.
After the repair, I did receive a warning (from vs installer) about update 3 failing to update but I restarted the computer and sln files can now open without needing that version dialog. Everything seems to be compiling and running fine as well.
Just ran into this situation for VS2017 then I realized I have unfinished updates for Visual Studio when checking Visual Studio Installer.
The installer displayed a hint that I should restart my computer to complete the update and after doing so, the version selector works again.
I often use command line tools to do source control updates of files and projects that I have loaded into Visual Studio 2010. With previous releases when I did this I could force Visual Studio to notice and load the changes by doing a Save All. This doesn't seem to work in Visual Studio 2010.
I do have 'Detect when a file is changed outside the environment' checked in the Options window, but if I sit and wait it takes minutes or longer for the changes to be noticed.
How can I force 2010 to notice the changes in loaded source files and projects?
You can reforce reloading a project by unloading and loading the project.
Right-click the project and select Unload Project, then, when the project is unloaded right-click again and select Reload Project.
Note that this requires that all modified files in the project either be saved or the changes in the file be discarded.
It sounds like this could be the same problem that I experienced here. VS 2010 doesn't seem to pick up on file changes made outside the IDE (like if you add a file to the file system, and then click refresh in Visual Studio you don't see the new file, I experienced this on C++ projects).
You can refer here for the MS case, they claim they have fixed the problem in "the next VS release", which I assume would mean the first service pack for VS 2010.
Win7 shouldn't be a pre-requisite, though its possible an earlier edition (pre-SP1) of Visual Studio didn't work it. Upgrade always works, for reference the track changes option also needs to be turned on.