I am using Visual Studio 2013 together with TFS 2012 since a few weeks. Until yesterday I always had the Comments Textbox in the "Pending Changes Window". Now it has dissapeared and I can not find a way to get it back. This is a serious problem since it is mandatory to give comments to every checkin.
Can anybody tell me how to get the comments textbox back.
Can you post a screenshot of your Pending Changes window? It should be right here:
I recently had to struggle through this issue myself and found there is very little information out there on how to resolve it.
For my situation, what finally fixed the issue was removing the 2012 version of TFS Power Tools and upgrading to the 2013 version. There are several members of my team who are using the combination of TFS Power Tools 2012 and VS 2013 with no issues, I'm the only one who saw this.
I suspect that this was not a power tools issue as much as it was a problem with VS caching some TFS data locally. I tried a number of options to clear caches in both VS and TFS and nothing worked until I did this uninstall/reinstall.
Regardless, after the TFS power tools upgrade and a reboot, the Comment box was back. Hope that helps!
EDIT: I should also point out that not only was my "Comments" section missing, I also had no "Policy Warnings" section which we require on certain projects of our TFS.
I had exactly the same issue right after installing NCrunch 2.4.
Uninstalling it brought my comment box back.
Having the same issue. Vanished today. Have not installed anything for weeks. I had 3 Visual Studio 2013 up at the same time. 2 was bugged, 1 was not. I closed the 2 buggy ones, and then the working one hoping that last one would save its settings last. Did not work. Now I have no way of adding comments. I can check in anything without the policy blocking me like it normally does when I do not enter a comment.
UPDATE: A simple reboot of the client solved it. The Comment is back!
Related
I have recently issued a Changeset Comment Policy in my team projects, following the steps at https://stackoverflow.com/a/13981350/2713582.
Thing is, even when someone supplies a comment on the changeset, it still shows up a policy override window, stating that the field is blank. Oddly enough, It does not happen in my machine.
We're using VSOnline, alongside with VS2010 and Windows (8.1 / 10).
Did anyone ever face this issue?
If you are using VS2010 and can't check in the code.You have missed the last paragraph with the above tutorials page.
Note: In Visual Studio 2010, you will have to install the Team Foundation Power Tools on all client machines - those without it installed will not be able to check in code.
I'm having this error pop up once I start Visual Studio professional 2013 with update 3.
I don't know whats going on and also when I created a web form and try to put items from the toolbox into a table in my code it doesn't let me. the items are dim and can't select them any more. before I would make a table and try to add Labels, textbox, etc and it wasn't a problem.
Visual Studio 2013 Update 4
Tools -> Extensions and Updates
Disabled "Release Management for Visual Studio 2013 v2.1".
That worked for me.
I got the same issue today, but the error message should be giving you some guidance.
Take a look at mine, it tells me to check the "ActivityLog.xml" for more information.
After looking at the entry my error showed me that it ocured the evening before around 5:30pm and I know I was installing the Visual Studio 2013 Update 4 at this time. So it seems I had a problem with my Update installation.
(Sorry maybe someone can school me on how to properly load an image for viewing)
So I realized my problem was an install issue I created, yours might be an add-on or something similar that you just updated your Visual Studio with that corrupted your VS.
So a little more researching and asking some buddies at work and we tried doing this step in another SO article, which should have the same effect of fixing our package loading problem also.
the Provider package did not load.
After running the steps listed there my Visual Studio started up without any obvious issue.
Hope this helps.
Open ActivityLog.xml in a viewer (I've used Microsoft Edge) and you'll find the error. VSPackage is the "Developer Analytics Tools" extension for me.
The error is gone after uninstalling that package. You can obtain the package and attempt to reinstall from the Developer Analytics Tools page in the Visual Studio Gallery.
I uninstalled and reinstalled Visual Studio and the problem went away for a little bit. It eventually came back complaining about different packages.
Then I noticed my home directory was encrypted. I decrypted the directory and the problem went away.
If it is not an encryption issue, I'd try just uninstalling and reinstalling VS 2013.
Message could be shown in case of "Path" environment variable longer than 2048 characters. In that case, system doesn't work proply with system paths like %windir%.
If it's your case, shorten "Path" environment variable and everything works again.
I've recently tried to install ReSharper 8.2.1 on my new computer for Visual Studio 2013. The install process succeeds but when I open Visual studio, there is no ReSharper Tab at the top.
In Tools -> Options, ReSharper is there and i can click the Suspend Now button, but the Options.. button has no effect.
Is there something i'm missing? or a setting I have forgotten?
I had the exact same problem. I tried reinstalling it with admin privileges, repairing it, suspending and restarting it etc. but nothing seemed to work. I eventually deleted the %AppData%\JetBrains\ReSharper as stated by some people in the comments on this post, which finally fixed everything.
http://resharper-support.jetbrains.com/entries/21204867
I solved it updtating ReSharper.ExternalAnnotations to the last version like this answer mentions.
If you don't have it yet you can download it by going to
Resharper => Extension Manager => Updates => Resharper.ExternalAnnotations
I spent almost an entire day getting Resharper 9.2 working with VS 2013 Premium.
Followed the steps mentioned at http://resharper-support.jetbrains.com/hc/en-us/articles/206104038-ReSharper-is-not-available-in-Visual-Studio-after-installation without any success.
Finally what worked for me was to repair the VS 2013 setup.
(This is not relevant to the question posted as the question is for Resharper 8.1. However, I am posting this as someone might find it useful and may not end up wasting time like me!)
What's the reason for error message "The snapshot is out of date and cannot be used anymore because type tree has been updated, A new snapshow needs to be acquired"?
This error appeared right after I launched VS2010 and added username/pwd to connect to TFS repository.
I am using VS 2010 professional edition.
It happened to me with VS2012 as well after loading the project without source control binding, a local simple WinForms project. All I needed to do was Clean & Rebuild. After that the problem was solved.
This is a bug in Visual Studio. According to http://connect.microsoft.com/VisualStudio/feedback/details/742959/the-snapshot-is-out-of-date "We've taken a closer look at this problem and it isn't one that we'll be able to solve in the next release of Visual Studio."
They recommend waiting around until the background language parser service is done (or, in other words, don't try to be too productive there partner.) My experience is that closing all documents, cleaning the solution, rebuilding it and then closing and re-opening with a pause after does remove the error.
Until you do something silly, like edit code. Then all bets are off again as to when it reoccurs.
I had a similar issue with VS2012 and after rebuilding the solution twice, I still saw the same error message.
Following an advice from a post from this site, I closed the Designer tab, reopened it from the Solution Explorer, and the problem was resolved.
I got this error too, but after I unload project and reload project, the problem was resolved.
Simply restarting Visual Studio 2012 was a workaround for me, but it kept happening about every hour and having to restart visual studio that often was very annoying.
I also found this post which suggests that the Productivity Power Tools are the problem and to simply turn off the Automatic Brace Completion in Tools->Options->Productivity Power Tools. Since making this change I haven't seen the error message again :)
I'll note though that I am using Visual Studio 2012 and the OP is using Visual Studio 2010, but the Productivity Power Tools are available for VS 2010 too, so this may still fix the problem in VS 2010.
The same issue persists in VS2013, but no amount of Clean/Rebuild or restarting VS will help. The only way I can do a successful publish, is to disable the AutoT4MVC extension.
I got this error too. I closed Visual Studio 2012 and opened it again and the error was gone.
I got this error when I had conflicting class names / namespaces. I was referencing a UserControl from a different DLL in my XAML file which had the same name as my XAML file (class name). Maybe this helps.
I used Visual Studio 2012, and just faced this error on my Windows 8. It seems like Turning off the VM and restarting Visual Studio fixed the issue.
I just got this with VS2010.
I had a form with a user control (UCa) with a user control (UCa) from a different project on it. Made a change to the UCb then flicked to the designer for the form and boom! Snapshot error.
Resolved by a full clean and then rebuilding just the UCb project before building the rest of the project.
I'm using Visual Studio 2012, and I got this error when starting Visual Studio, letting TFS connect to the server, and THEN opening my solution. The fix was simply closing VS and launching the solution directly.
I'll throw my two cents in here as well.
I've tried every combination of Clean, Rebuild, Restart, etc. What I've found is that restarting Visual Studio usually makes the problem go away for at least one Publish. Here's the weird part, though. You can also fix the problem by doing absolutely nothing. If you just let Visual Studio sit for about a minute or two, and then publish, it will usually work just fine. There's some background voodoo going on here, and waiting for it to finish seems to do the trick.
I have a solution with two parts that need published. One is a WCF service application, and the other is the ASP.NET MVC5 website itself. Anytime I publish the services, and then try to publish the site I'll see this error. I can publish the services, restart VS, and then publish the site, OR I can publish the services, go get a drink, and then publish the site. As long as I give VS a chance to "settle" between any kind of rebuild and the publishing of the site, everything seems to work as expected.
Take a walk, come back, problem solved. OR if you don't have the time. Clean, Rebuild, Restart, Publish (lather, rinse, repeat).
I've had a serious issue with my Visual Studio 2008 setup. I receive the ever-so-useful error 'A problem has been encountered while loading the setup components. Canceling setup.' whenever I try to uninstall, reinstall or repair Visual Studio 2008 (team system version). If I can't resolve this issue I have no choice but to completely wipe my computer and start again which will take all day long! I've recently received very strange errors when trying to build projects regarding components running out of memory (despite having ~2gb physical memory free at the time) which has rendered my current VS install useless.
Note I installed VS2005 shell version using the vs_setup.msi file in the SQL Server folder after I had installed VS2008, in order to gain access to the SQL Server 2005 Reporting Services designer in Business Intelligence Development Studio (this is inexplicably unavailable in VS2008).
Does anyone have any solutions to this problem?
P.S.: I know this isn't directly related to programming, however I feel this is appropriate to SO as it is directly related to my ability to program at all!
Note: A colleague found a solution to this problem, hopefully this should help others with this problem.
A colleague found this MS auto-uninstall tool which has successfully uninstalled VS2008 for me and saved me hours of work!!
Hopefully this might be useful to others. Doesn't speak highly of MS's faith in their usual VS maintenance tools that they have to provide this as well!
I had the same error message. For me it was happening because I was trying to run the installer from the DVD rather than running the installer from Add/Remove programs.
In my case, uninstalling from Add&Remove Programs didn't work. Instead, the problem was due to a recently hotfix installed through automatic updates. The hotfix to VS 2008 (in my case) has the number KB952241, so I uninstalled it using Add/Remove Programs checking on the show updates option. After it was unistalled the problem was gone.
I encountered the same problem and found a very easy solution.Go to the following Link:
http://msdn.microsoft.com/en-us/vs2008/bb968856.aspx
and run VS AutoUninstall tool .This will automatically remove all the components of VS 2008.
Cheers
Sure enough, for me, it was the hotfixes. In Add/Remove Programs, check the "Show Updates" box, and remove ALL of the Hotfixes associated with your version of VS2008. Then try the "Change/Remove" button - it should now proceed without a hitch.
Well, it did for me, anyway... ;-)
I have Visual Studio Team System 2008 Development Edition, and had to remove all updates and Hotfixes:
Update KB972221
Hotfix KB973674
Hotfix KB971091
Reboot, then the following Hotfix appeared, which I then removed as per #riaraos' answer:
Hotfix KB952241
Before the Change/Remove would work!
Hope that helps someone else.
Uninstall hotfixes installed in related to vs2008 and then try again.
It worked for me and hopefully it will for you as well.
Thanks,
Zelalem
Remove the following hot fixes and updates
Update KB972221
Hotfix KB973674
Hotfix KB971091
Restart the PC and try to uninstall now. This worked for me without problems.
Microsoft itself posted a KB article about this, and that article has a service pack that they claim fixes the problem. See below.
http://support.microsoft.com/kb/959417/
It took a while for the associated update to install itself, but once it did, I was able to run the Visual Studio setup successfully from the Add/Remove Programs control panel.
You should look for the MSI setup logs in the temp directory of your system. They will contain detailed inforamtion about why the setup failed.
I had a similar installation problem with Visual Studio 2008 which I was able to resolve by studying the logs.
I think this sort of question is entirely appropriate to the forum, especially if an easy solution can be found, as would save others hours of pain.
Unfortunately I dont have the solution, but would suggest (if you haven't already)
Run FileMon to see if the
installer is looking for specific
files which are no longer there -
this may give some clues.
Painful, but try uninstalling other apps based upon the VS shell (eg 2005) first.
Thanks, riaraos, uninstalling KB952241 was the solution for me, too. Before doing that I tried to run the installer from "Programs and Features" and from the installation DVD without success. I did not want to completely remove the VS 2008 installation but only add a few components.
Notes on my system:
Windows 7 Beta 1
Visual Studio 2008 SP1
Okay I had the same issues first my VS2008 was acting up so i tried to uninstall it and it didn't work...I read online that using an AutoUninstall by MS will do the trick it did just that , but left a lot of nasty files behind..
So i used "Windows Install Clean Up" and cleaned up more stuff that had to do with VS..
then went back into Add and remove in control panel Removed the KB952241...
then opened up Ccleaner and scanned the registry found a lot of left behind crap from VB2008 removed all that once that was done.
I went ahead and launch the installed back from the CD again and BAM its working.
I did all this without having to restart my PC..
Hope this helps people who are stuck..like i was
In my case, installing visual studio SP1 unbroke the uninstall/repair functionality.
Windows 7 suggested to "Uninstall using recommended settings" after hitting OK in the error message. It solved the problem.
Solution to this is
http://www.dotnetzone.gr/cs/forums/48758/ShowThread.aspx#48758