tfsbuild

Is there there a property that can be used in either a Visual Studio build or a TFS build that will always point to where the binaries are? Meaning that when I build in Visual Studio it will point to C:\MySolution\MyProject\bin\Release and in a TFS Build it will point to C:\Build\Path\MySoution\Binaries And if there is not one, why not? This seems like a common, basic need/feature. There is an $OutDir property, which you can use in things like post-build events. In a VS2010 build, it will be a relative path from the current project to the binaries, so it will be "bin\Debug\" for example. (The

How can I rename a file in a release definition in Visual Studio Team services? Is there a built-in or marketplace task available or otherwise, how can this be achieved? Answer: Add the "Inline PowerShell" task from the marketplace Enter the following PowerShell code in the text area Param ( [string]$pathToFileToRename ) Rename-Item $pathToFileToRename NewName.txt Enter any required arguments in the arguments text box (you can use environment variables), for example. pathToFileToRename $(System.DefaultWorkingDirectory)/somepath/CurrentName.txt Use the Run Command Line task or do it in a

I am trying to write a PowerShell script, but I'm running into an error. When my script gets to the line $tfs = [Microsoft.TeamFoundation.Client.TeamFoundationServerFactory]::GetServer($server) I get the error: Unable to find type [Microsoft.TeamFoundation.Client.TeamFoundationServerFactory]... InvalidOperation: (Microsoft.TeamF...onServerFactory:TypeName) [], RuntimeException Though my question is very similar to this question , I already know that the Microsoft.TeamFoundation.Client.dll file and its dependencies are in the GAC. The other question never clarifies that, and I think that might

First some context; we are developing a large desktop WPF application in .NET 4.5 targeting 64 bit Windows 7 and 8. We are using Visual Studio 2012.2 (soon to be .3 then probably 2013!) and TFS 2012 (again .2 soon to be .3 then 2013). Currently this product is all in a single large solution (just over 50 projects) yielding a WPF exe, a load of dlls and a nice MSI to install it. We use TFS (gated and scheduled) to build the solution, its installer (WiX) and run its tests (SpecFlow for BDD and MSTest unit tests) and this is working very well. I have a separate scheduled TFS build that deploys

I'm trying to build my solution and package up the web app into a web deploy (.zip) package to be deployed. I've added the Visual Studio Build step with the following MSBuild Arguments: /p:DeployOnBuild=True /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:PackageLocation="$(build.artifactstagingdirectory)\" And I've set up the Copy and Publish Build Artifacts step to copy all .zip files to the drop folder. The build completes successfully but nothing is copied to the drop folder because there are no .zip packages that get created. So when I look on the TFS server, the only thing in

I am attempting to use Visual Studio's Team Explorer and TFS to create a Build Definition to deploy a MVC site to IIS. I followed the Pluralsight tutorial called 'Continuous Deployment with Team Foundation Server 2010'. The steps I followed from the tutorial included: Installed IIS Management Scripts and Tools Installed Management Service On the Management Service I allowed remote connections and enable Windows Credentials Only Installed Web Deploy Created a deployment domain account Allowed domain account permissions to modify IIS file system Set delegation rules using this domain account Set