build-server

I haven't worked for very large organizations and I've never worked for a company that had a "Build Server". What is their purpose? Why aren't the developers building the project on their local machines, or are they? Are some projects so large that more powerful machines are needed to build it in a reasonable amount of time? The only place I see a Build Server being useful is for continuous integration with the build server constantly building what is committed to the repository. Is it I have just not worked on projects large enough? Someone, please enlighten me: What is the purpose of a build

Its been a while since I setup a Build Server so maybe I've forgotten something or maybe .NET 4.5 is different from whatever version I did this with last time, but here is my problem. I'm trying to setup a build server to monitor a source control repository. Whenever something changes, I want the server to pull the changes and build the project. If there are no errors, I want to deploy the site to a web site running on the build server. In the past when I did this, I thought that I was able to do this having only .NET installed, but when I try to build this project I get an error that "C:

I want to use mstest.exe to run my unit test on build server, but I don't want to install Visual Studio on the build server. Can I just install MSTest without Visual Studio? Bela It is possible to run mstest.exe without visual studio. Download one of the Agents for Visual Studio ISO's below and install the Test Agent on the server: Visual Studio 2017 (127MB disk space, less than that for download) Visual Studio 2015 (128MB setup, 2GB disk space required) Visual Studio 2012 (224MB) Visual Studio 2013 (287MB) Visual Studio 2010 (515MB) This installs everything needed for running mstest.exe from

When creating a new build in Team Foundation Server, I get the following error when attempting to run the new build: The path C:\Build\ProductReleases\FullBuildv5.4.2x\Sources is already mapped to workspace BuildServer_23. I am unable to see a workspace by that name in the workspaces dialog. NotMyself Use the command line utility TF - Team Foundation Version Control Tool ( tf ). You can get a list of all workspaces by bringing up a Visual Studio Command Prompt then changing to your workspace folder and issuing the following commands: C:\YourWorkspaceFolder>tf workspaces /owner:* You should see

Historically, this has been done with the Microsoft Build Tools . But it seems that the Build Tools may not be available for versions after 2015 . The replacement appears to be the Visual Studio build tools, which doesn't seem to have a real homepage yet. I downloaded the VS2017 Professional installer , and went to the Individual Components tab. Right away, the summary is telling me that the Visual Studio core editor is there, taking up 753MB. I don't want the editor. Just msbuild. There is no way to unselect the editor. Is there a way I can install the latest version of msbuild without also