tf : The term 'tf' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and
try again.
I set up the environment variable but does not work. tf command works in Developer Command Prompt for VS2013 but does not work in Powershell. How can I make this to work?
You need to include tf.exe full path. For example, you want to check in files with tf checkin command in PowerShell:
$filePath = "C:\Users\username\Source\Workspaces\teamproject\solutionname\projectname\Class1.cs"
Set-Alias tfs "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\tf.exe"
tfs checkin $filePath /noprompt
This worked for me. I added the path of TF.exe
("C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE" in my case) to system environment PATH variable (through My Computer->Properties->Advanced System Settings->Environment Variables->System Variables->Path->Edit).
You can check if "tf" is working by typing "tf" in the powershell. If you get an output something as :
Microsoft (R) TF - Team Foundation Version Control Tool, Version 14.102.25619.0
Copyright (c) Microsoft Corporation. All rights reserved.
......
tf is working properly.
To answer the question form another perspective, this is how you are supposed to call the tf environment variable you created:
%tf%
I've given it the value C:\Windows\notepad.exe, and the application opens when calling the variable from cmd.
You need to download and install the Microsoft Team Foundation Server Power Tools in order to run the TFPT command.
TFS 2015 version can be found here:
Microsoft Team Foundation Server 2015 Power Tools
If you run the Powershell from VS Tools then you need to close your Powershell session and restart your VS in order for it to pick up the newly installed tools and run the Powershell again.
Related
We have configured a windows virtual machine and deployed an agent there to build our code and run scripts.
In our VM we two different flavors of PowerShell command prompt:
Windows PowerShell
Developer PowerShell for VS 2019.
How can we start "Developer PowerShell for VS 2019" from our pipeline YAML script and execute our checked out .ps1 file there?
There are several flavors of PowerShell tasks that can be initiated from the pipeline though and not sure which one of them will serve the purpose. They are the following:
Azure PowerShell
PowerShell
PowerShell on Target Machine
Service Fabric PowerShell.
Which of the above represent "Developer PowerShell for VS 2019"?
The reason behind this specific flavor of PowerShell is:
Need to have some of the .NET Framework Tools (CorFlags.exe) which are only accessible in the "Developer PowerShell for VS 2019" and not in the other one.
The Developer PowerShell for VS 2019 is a regular PowerShell with a module imported, you can see exactly what in this way:
Go the Start menu and search for Developer PowerShell for VS 2019.
Right-click on it and Open file location - you will get this:
Now right-click again on the Developer PowerShell for VS 2019 shortcut and Properties.
You will see in the location that is run the regular PowerShell with some command:
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe -noe -c "&{Import-Module """C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\Microsoft.VisualStudio.DevShell.dll"""; Enter-VsDevShell bc97b47b}"
Now, if you open a PowerShell and run the script there:
&{Import-Module "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\Microsoft.VisualStudio.DevShell.dll"; Enter-VsDevShell bc97b47b}
You will get the Developer PowerShell for VS 2019 and CoreFlags.exe will work:
So, you need to use the regular PowerShell task (your option 2) and run the above command at the begging of the script.
Note: you should copy exactly the command you see in the Properties, in each machine it could be different.
Not sure how to do this... I work mostly on OSX and linux systems, so when I install an app or use for example G++ or xcodebuild, I just call it from terminal.
On Windows, I did install msbuild with VS2015, but if I am in powershell or regular command prompt, typing msbuild result in an error. I have to specify the whole path to make it work.
What is the equivalent in Windows world, of setting console so when I type msbuild, it gets the correct path?
You can set your path like so in:
PowerShell
$Env:Path = "<Path_to_msbuild>;${Env:Path}"
Batch/Cmd
set "PATH=<Path_to_msbuild>;%PATH%"
Note: The <path_to_msbuild> is the folder where msbuild.exe exists, and NOT the direct path to the executable itself
How it works
This will add the msbuild binary to your path, so you can invoke it from anywhere!
To verify which location msbuild is running from you can simply run (in both languages!):
where.exe msbuild
If you create just a link to msbuild you still won't be able to call for example the compiler from the command line. Which is why VS provides a convenient (pretty much canonical) way to do this by supplying a batch file which sets up the PATH and all the other build-related environment variables.
Example if you are on cmd.exe:
> "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\VsDevCmd.bat"
> msbuild
Microsoft (R) Build Engine version 14.0.25420.1
...
> cl
Microsoft (R) C/C++ Optimizing Compiler Version 19.00.24213.1 for x86
...
You can invoke this from the Start menu as well: hit start, type pro vs to look for matches, select Developer Command Prompt for VS2015.
For PowerShell (which I'd recommend spending time on instead of cmd) you'll need an extra function like presented here: https://stackoverflow.com/a/21652729/128384
I was trying to use my favorite source control from the Package Manager console in Visual Studio 2010. I had issues described in another topic. For now the best answer is to move all command-line stuff from Visual Studio to bare PowerShell.
But this case the Visual Studio related commandlets are not working. For example, most crucial one — I cannot run Update-Database command from Entity Framework.
Is it possible to register somehow Visual Studio specific commandlets for the current project in PowerShell? Or make PowerShell automatically take current project context from the packages subfolder?
The NuGet PowerShell commands rely on being run from within Visual Studio so will not work outside in the normal PowerShell running from the command line.
You can however use migrate.exe which ships with the EntityFramework NuGet package and use that from the command line to update your database.
As a prototype I put together a way to use NuGet PowerShell commands from the normal PowerShell command line using SharpDevelop. Unfortunately at the moment the EntityFramework NuGet package does not work with SharpDevelop.
Another interesting project is StudioShell which provides a new DTE: drive inside Visual Studio but can also be used outside from the command line. I do not believe it supports NuGet PowerShell commands being run from the normal PowerShell command line.
I can find the NuGet.psd1 file at:
C:\Program Files (x86)\Microsoft Visual Studio
12.0\Common7\IDE\Extensions\5ttpefif.3mk\Modules\NuGet\NuGet.psd1.
However, when you try to load it:
PS> Import-Module $pathToNuGetPsd1 -Force -NoClobber -Scope Global
Import-Module : The name of the current Windows PowerShell host is: 'ConsoleHost'.
The module 'C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\
Extensions\5ttpefif.3mk\Modules\NuGet\NuGet.psd1' requires the following Windows
PowerShell host: 'Package Manager Host'.
I think we're out of luck. It has to be run from the Package Manager Host and requires things from Visual Studio as stated by Matt.
To solve my problem I used Chocolatey to install NuGet.CommandLine and then used NuGet.bat to do what I needed. It is a little more work and may not work in all cases depending on what you're trying to do.
Chocolatey: https://github.com/chocolatey/chocolatey/wiki/Installation
NuGet.CommandLine:
PS> cinst NuGet.CommandLine
I'm not terribly familiar with the Visual Studio cmdlets, but you can import a module into your PowerShell session by using Import-Module -Name <ModuleName>. You can list the available (aka. "installed") PowerShell modules by using `Get-Module -ListAvailable'.
My guess would be that the Visual Studio cmdlets are contained with its own PowerShell module, but it's quite possible that it's not "installed" to one of the standard locations in $env:PSModulePath. If this is the case, then you might need to locate the module directory and import either the .psd1 or .psm1 file directly, and pass that into: Import-Module -Name <FullPathToModuleFile>.
As an example of the above, take notice of where the Windows Azure PowerShell module is located: http://trevorsullivan.net/2012/06/07/introducing-microsofts-official-windows-azure-powershell-module/
It's under the Program Files directory, and is not immediately available to PowerShell, unless you import the module from its fully qualified path (the .psd1 module manifest file).
Hope this helps.
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.
I have a Powershell script written in the version 1.0. In this existing old script I need the facility to get the latest code of a project from TFS. I have TFS client on the machine and that lets me use the TFS command line. I have created the TFS command line comments to get the latest from TFS. These commands run successfuly from the command propmt.
Now the I need to include these TFS commands in my old poweshell script. I need to know if this is doable? If yes then how.
Thanks.
One option is to run the TF.exe program with the necessary arguments from within your PowerShell script, as you would with any other executable:
PS> & "$env:ProgramFiles\Microsoft Visual Studio 10.0\Common7\IDE\TF.exe" #("workspace", "/new", "WS1", "/noprompt", "/login:foo,bar", "/collection:baz/tfs")
Or you could use the TFS PowerShell cmdlets included in the TFS Power Tools:
PS> Add-PSSnapin Microsoft.TeamFoundation.PowerShell
PS> Get-TfsChangeset -Latest -Server "http://mytfsserver"