I am aware that in the past, this was possible via TFS Power Tools, but that seems to have been deprecated.
You can use tf command, if you installed visual studio 2017 or 2019.
Open Developer Command Prompt for VS, and run below command.
Tf.exe status /collection:"<project collection URL>" /user:* /recursive
tf.exe is now integerated with VS2017/VS2019. You can find it in Visual Studio installation folder (eg. C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer)
I am adding TFS to Visual Studio Code IDE(1.42.0) for that I have installed Azure Repos extension.
In VS code at File-->Preference-->Setting-->Tfvc:Location, when I am entering path C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\tf.exe.
Getting error
(team) Unable to find the TF executable. Please ensure TF is installed
and the path specified contains the filename.
How can I solve this issue?
Edit 1: After installing Azure Repos extension, I am entering above path in tfvc:Location(for both tabs User and Workspace), but after entering path nothing happens. Check below screenshot
Edit2: Now I am getting this error at right below in VS code IDE
Since you have not got any help yet. I will take a shot. Any chance there is a issue with finding the executable and casing for the extension? My local TF is capitilized. \TF.exe
Also might want to checkout the Github and readme for TFVC.
Make sure you have installed VS on your computer. With a typical installation of Visual Studio, the Windows version of the TFVC command line client (tf.exe) is available under the Program Files (x86) folder. It will typically be placed in a location similar to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe. On the 2017 version of Visual Studio Community, it can be found in a location similar to C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\TF.exe.
I found a .vscode folder in my project
delete it, close and reopen vscode solved the problem
I am trying to call tf.exe from within a Powershell step of a TeamCity build configuration.
The executable is usually found at C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe (or similar). In my script I am setting a variable to the path of tf.exe as follows:
$tfsExe = "%env.ProgramFiles(x86)%\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe"
I have verified the existence of tf.exe on the build server by accessing it through RDP. I have also called it in a powershell console window with the following command
& "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\tf.exe" help
which responded with the following output confirming that it is accessible and working:
Microsoft (R) TF - Team Foundation Version Control Tool, Version 11.0.50727.1
Copyright (c) Microsoft Corporation. All rights reserved.
Type tf help <command name> for command line description.
Type tf msdn <command name> for full documentation in Microsoft Document Explorer.
Commands:
tf add Adds new files and folders from a local file system location to Team Foundation version control.
tf branch Copies an item or set of items, including metadata and version control history, from one location to another on the Team Foundation version control server and in the workspace.
The issue here was that the script was being executed on a build agent not the build server. Once the TFS plugin was installed on the build agent tf.exe was available.
Every time I install a new program that uses command prompt it still does not recognize it. For example, I have installed git and nodejs and added them to the %PATH%, but they are still unrecognizable in my command prompt.
%Path% = C:\Program Files (x86)\WANdisco\Subversion;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.0\Windows Performance Toolkit\;C:\Program Files (x86)\Git\cmd;C:\Program Files (x86)\nodejs
If any other system variables need to be posted, let me know! Thanks in advance for the help!
Don't use
%Path% =
Use this:
Path=
and it will be modified for the scope of the batch file.
To make it global so it is available in every cmd prompt you can use SETX or modify the Windows environment variables in control panel, system, advanced.
I was tring to deploy an ASP.NET Web Application to a Windows Azure Web Site by following the tutorial through this link: https://www.windowsazure.com/en-us/develop/net/tutorials/get-started/
After download the public profile, which is a ".PublishSettings" file, I go back to Visual Studio and right-click the project in Solution Explorer and select Publish from the context menu as the tutorial said. However, a warning box jumped up and it showed me that "The Web Publishing extension is not installed which is required to publish. You can install it from http://go.microsoft.com/fwlink/?LinkID=208120."
I already installed "Windows Azure SDK for .NET (VS 2012)" and I also tried to uninstall this and install again, but the same problem is still there.
Anyone knows how to solve this? I am really appreciated.
I ran into 2 issues, which were related. One was the web publishing extension is not installed which is required to publish, and the other was the web extension package did not load.
I'm upvoting and reposting user3918092's solution for others who run into this issue and do everything including:
Deleting the ComponentModelCache out of
C:\Users\...\AppData\Local\Microsoft\VisualStudio\12.0 and
C:\Users\...\AppData\Roaming\Microsoft\VisualStudio\12.0
Repairing Azure SDK 2.4 and VS2013U3 Uninstalling and reinstalling
both Azure SDK 2.4 and VS2013U3
Removing extensions from the solution
Ignoring the extensions on VS startup
Using devenv /setup and devenv /updateconfiguration to try to reset the configuration
The solution is:
Reinstall the following items to your GAC using the following commands from the vs command line run as an administrator:
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Internal.Contracts.dll"
Thanks to user3918092!
I had the same problem on Visual Studio 2013 (Asp.net and web tools 2013 extensions have not been installed)
Solve it by re-install Visual Studio 2013 update 3.
http://www.microsoft.com/en-us/download/details.aspx?id=43721
This has worked for me.
I had Visual Studio express 2012 then installed Visual Studio 2013 needed the azure tools so I installed 2.4. I lost publishing at this stage and
unistalled Visual Studio express 2012.
So that is how I think it got out of kilter.
The solution was to reset the assemblies for Contract and Publishing using the Developer command prompt as Administrator.
If you have used the default installation setting then this is probably the path
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Internal.Contracts.dll"
Same issue with Visual Studio 2015.1 after installing a Web Tools update.
The assmeblies that have to be installed into gac are now:
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.Core.Contracts.dll"
gacutil -i "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Microsoft\Web Tools\Publish\Microsoft.VisualStudio.Web.Publish.Contracts.dll"
I have the same problem. After reinstalling VS 2013 update 4 and Azure SDK 2.6 problem still persists.
But then I tried the next thing:
In section Control Panel > Programs > Programs and Features select and repair Microsoft ASP.NET and Web Tools 2013.4.
And publish option started to work again.
I had this issue upgrading VS 2013 Ultimate from update 3 to 4. I had also a message about Microsoft.VisualStudio.Web.PasteJson.JsonPackage did not load properly when loading a Solution.
Repairing VS was enough for me to work again the publishing option.
http://connect.microsoft.com/VisualStudio/feedback/details/758298/not-able-to-publish-web-application-after-installing-visual-studio-2012-rtw has a work-around but it's a painful reinstall with additional folder deletion.
register GAC also work when have this problem after update VS 2013.2 to VS 2013.3
I had similar problem, but my error is related to scaffolding item.
I need to uninstall visual studio and went through all the related folders, registry and re-install visual studio in order to make it work!
Folders that I checked:
%App Data%
%Program Data%
%Program Files%
Windows
Hope that help :)
I uninstalled VS2012 again. Before I re-installed (a 3rd time), I went to my user's AppData and Documents folders and found all instances of Visual Studio 2012 and deleted them. Then I re-installed VS2012 and now Web Publishing is working.
Folders I deleted after uninstall:
C:\Users\USERNAME\Documents\Visual Studio 2012
C:\Users\USERNAME\AppData\Local\Microsoft\VisualStudio\11.0
C:\Users\USERNAME\AppData\Roaming\Microsoft\Microsoft Visual Studio\11.0
C:\Program Files\Microsoft Visual Studio 11.0
C:\Program Files (x86)\Microsoft Visual Studio 11.0
I had this happen today out of the blue for a vs2013 project that was publishing fine previously.
I solved it by downloading a 'Visual Studio Web Publish Update' package from here.