TFS Client Error using Visual Studio 2010 - visual-studio-2010

I have been getting this strange error with VS2010 TFS client, whenever i try to do
any operation related to TFS.
Method not found: 'System.String
Microsoft.TeamFoundation.VersionControl.Client.ExtendedItem.get_LockOwnerDisplayName()'
More background : I was working with TFS build services on my machine and
later I uninstalled the TFS build services .. And after that i started getting this problem.
Also I repaired VS 2010 (Pro edition) and also re-installed VS 2010 SP1 .
Reinstalled TFS build services, reinstalled tfs power tools also
But still the problem persists.
Any clue how to repair/fix this?
Any way to fix the TFS client part of VS2010 ?

After installing the following hotfix,the problem was fixed.
FIX: A hotfix for Visual Studio 2010 SP1 is available to add compatibility support for Visual Studio Team Foundation Service Preview
Intresting point from the above site :
Note The following hotfix includes all the Team Foundation Client
hotfixes that were released after Visual Studio 2010 SP1 was released.
Hope this is helpful to others too.
(I guess this must have refreshed my VS2010 TFS client files)

Another solution :
Bind and rebind the project to the TFS server.
It has solved the problem in my case.
Good Luck.

This same issue happened to me after Windows Update installed update KB2813041 to Visual Studio 2010. After I uninstalled this individual update, it started working again.
Here's how to uninstall an individual update. Go to Control Panel > Windows Update > View Update History > Installed Updates (appears in a sentence at the top of the dialog). Then, scroll through the list of updates looking for Visual Studio and then right-click on the update you want to uninstall and click Uninstall.
Hopefully this helps somebody.
Thanks,
Andy

Related

Install SSDT for Visual Studio 2017 community fails on recursion too deep

"Setup Failed" Recursion too deep; stack overflowed 0x800703E9.
I have windows 10 and newest visual studio version. I have tried rebooting to make sure I have as many resources as possible. I have 4g ram.
If the SSDT installer gives you multiple instances of Visual Studio to choose from, try the "new" option.
I ran into this problem trying to install SSDT 15.8.1 on Windows Server 2012 R2 with the latest version of Visual Studio 2017 (v15.8.6) already installed. The SSDT installer gave me 2 options in a dropdown box.
Install tools to this Visual Studio 2017 instance:
Visual Studio 2017
Install new SQL Server Data Tools for Visual Studio 2017
When I chose the first option: Visual Studio 2017 (presumably the existing instance), I ran into the cryptic "recursion too deep" error. I installed the SSRS extension for VS (as suggested by others on Stack Overflow) and tried running the SSDT installer again for the existing Visual Studio 2017 instance. I got the same "recursion" error.
I tried one more time, but this time chose the 'Install new SQL Server Data Tools for Visual Studio 2017' option. This time the install process completed!
Apparently there is an installer inconsistency between the latest versions of SSDT and Visual Studio. The suggested fix is to start with a previous installation of Visual Studio 2017, install the latest SSDT on top of that, and then upgrade Visual Studio. This is a very time consuming fix. It appears this is only necessary for the SSIS components - the SSAS and SSRS pieces are available as Extensions within VS, and I believe they still install successfully from there.
https://developercommunity.visualstudio.com/content/problem/258117/ssdt-failed-to-install-vs-2017-pro-1572.html
Please re-run the VS community 2017 installer or go to Control Panel-Programs and Features, uninstall the previous SSDT version for VS 2017, then re-install it, you can have a look at this similar issue.
If this issue persists, please use http://aka.ms/vscollect to gather the installation logs and find vslogs.zip under the %temp% folder, then upload the file to Onedrive and share the link here.
You should uninstall the current version of SSDT before install a new version.
If your computer have some pages blocked, you could download the specific version offline installer (Download the header, then use SSDT-Setup.exe /layout [Folder]) for the former version and new version of SSDT.
How I got past it:
Uninstall the Visual Studio extensions for Reporting Services (and Analysis Services) projects in case if you going to select them during SSDT set up. Note: remember to run VS as administrator to do the uninstall.
Reboot VS2017 (just out of general principle.)

Team explorer 2015 View Builds generate Malformed Artifact URI error

I am having an issue with Team explorer in visual studio 2015 Update 1 RC.
The server is TFS 2013.
When I want to View Builds of a specific build, I have this error message
Malformed Artifact URI: [Build name]
Parameter name: uri
This is working using Visual studio 2013 on the same machine, and working with visual studio 2015 on other machine. So this is not a problem with the server.
Only 2 machines have the issue, and both have the extension TFS power tools 2015 installed.
I tried:
Remove the extension
Clear Team foundation cache
Repair visual studio
Hard reset all settings
Didn't resolve the issue.
"Edit build definition" and "Queue new build" are working.
Any ideas other than uninstall and reinstall visual studio?
Thanks
Edit:
- Creating a New build definition in VS2015 is working, but trying to open it doesn't work
I can reproduce your issue in my Visual Studio 2015 just after the Update1 RC is installed.
Here is my Visual Studio version:
I have reported this issue. You can also submit one feedback on the Microsoft Connect site.
Now, you need to open TFS web access directly to view one build. Or you need to uninstall Update1 RC.
This issue is fixed in VS2015 update1. You need to download and install it: https://www.visualstudio.com/en-us/news/vs2015-update1-vs.aspx
Cleaning cache folder on your client machine: C:\Users\username\AppData\Local\Microsoft\Team Foundation\6.0\Cache. And clean the cache on your TFS AT machine: C:\TfsData\ApplicationTier\_fileCache
Then, on your client machine, resetting settings and add-in settings with devenv /ResetSettings and devenv /ResetSkipPkgs, try rebuilding all templates with devenv /setup.

VS 2013 Express for Desktop wont open vcxproj project files

I am trying to open the Direct3D Tutorial Win32 Samples with VS 2013 Express for Windows Desktop. To my surprise it claims that the individuals projects in the solution each cannot be opened because their project types (.vcxproj) are not supported by this version of the application.
Does anyone know why the vcxproj files cannot be opened, or how I could diagnose and repair the root cause of the problem?
Edit: I can also not open the vcxproj files in Mike Farnsworth's Rayito project.
It means that the projects were created in another version of Visual Studio.
Try to upgrade the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting Upgrade Solution.
Alternatively you could use Visual Studio 2012 Express Edition to see if that resolves the problem.
Windows Dev Center indicates that Visual Studio 2012 is required.
Hope this helps
Neither of the other answers seemed to help.
I uninstalled visual studio. I uninstalled SQL server. I reinstalled visual studio. Now it loads C++ projects correctly.
I understand a previous install of visual studio can cause the problem I was having. Apparently so can installing SQL server Express prior to installing Visual Studio 2013 Express.

Lightswitch not working in Visual Studio 2013

I'm having trouble getting lightswitch to work on my home computer.
If I try to create a new lightswitch silverlight project I get the following message:
If I try to open a project created on my laptop I see:
I've tried both to repair and reinstall visual studio with no change.
Any clues?
Have you installed it as an optional feature?
See this link:
http://social.msdn.microsoft.com/Forums/en-US/577ddba0-1440-43aa-8bba-18c587ee611f/open-project-lsproj-with-visual-studio-2013?forum=lightswitch
Specifically the install picture a few posts down:
EDIT: You may have to select "Modify" (depending on installer) to see that screen.
Which update of Visual Studio 2013 you have? As described here Update 2 CTP 1 has known issues and not recommended to install for LightSwitch development.
From Add/Remove Programs in the control panel, uninstall "SQL Server Data Tools 2013". Then re-install VS 2013 Update 1.
If the solution works, then you can try to reinstall SSDT by using the standalone installer.

Can you install VS2013 alongside VS2012 without issues?

I cam across this question here on SE:
Can Visual Studio 2012 be installed side-by-side w/ Visual Studio 2010?
According to one comment with a good amount of upvotes, having 2010 and 2012 installed at the same time can present issues. I then came across this MSDN page about 2013:
http://msdn.microsoft.com/en-us/library/hh266747.aspx
If you use Visual Studio 2013 together with Visual Studio 2012 or Visual Studio 2010 SP1, you can [blah blah]
That suggests that 2013 can be safely installed along with VS2012. Can anyone confirm?
Take a look at Brian Harry´s Blog post announcing Visual Studio 2013.
VS 2013 can be installed side by side with previous versions of Visual Studio or, if you have a VS 2013 pre-release, it can be installed straight over top of the pre-release. TFS 2013 cannot be installed side by side but can also be installed over top of either a previous version (TFS 2012 or TFS 2010) or a pre-release.
Looks like you can, yes.
You can install this version of Visual Studio on a computer that
already has an earlier version installed.
http://msdn.microsoft.com/en-us/library/ms246609%28v=vs.120%29.aspx
Only issue I can see is during uninstallation, where the file associations may get lost.
I was having two installation on my computer. Really no problems.
From personal experience, I've come across multiple issues with using Visual Studio 2012 and prior, while a VS2013 installation exists on a machine.
Some of the issues include built executables failing to launch (double clicking .exe does nothing, but debugging them in VS launches them), and inability to compile solutions that mix C# and C++ projects.
I would avoid 2013 until these issues are resolved, as just having it installed on a machine breaks older code, even if you don't use VS2013.
There are some minor (compatibility) issues between using both VS2010 and VS2012 on the same Solution, but simply having VS2012 installed on your machine won't effect anything in VS2010.
There may be compatibility issues with 2013 Community edition. I had VS 2012 Ultimate and VS 2013 Express installed and working without any issue, but as soon as I installed VS 2013 Community, my VS 2012 Ultimate install has been behaving unusually. When I first open VS 2012 U, there is a really long load time. When I perform some action (open a file, select a menu option, anything actually) I have to minimize and maximize VS 2012 U for the screen to refresh. I am still trying to figure it out myself - so if anyone has a solution, please share.

Resources