Best IT Recipes

Is MSbuild required to install Visual Studio on the build server?

Can I use MSBuild without Visual Studio 2012?

We currently have a build server, where we compile and create an instance of the deployment of one of our projects, Visual Studio Professional Edition is installed in it. Now we are creating a new build server. Do we really need Visual Studio 2012 on the new build server?

If so, how? I googled it, but I could not find the answer.

+44
build visual-studio-2010 visual-studio-2012 msbuild nant
Jun 30 '14 at 5:45
source share
7 answers

No, you do not need Visual Studio in the build window. If I remember correctly, msbuild is installed as part of the .NET environment - it certainly has always been.

Depending on what you are building, you may find that there are some things that are easier to get if you are installing Visual Studio - things like portable class library profiles. Although non-VS installers are usually available, I found it easier to install the Express version of Visual Studio only to get related build goals.

+30
Jun 30 '14 at 5:54
source share

We spent a lot of time trying to get our Build Servers to work without Visual Studio. We do not use TFS for assembly, and therefore I am not sure that the license exemption above applies to us. In addition, without having Visual Studio installed, you really understand how your software is created and whether links are referenced correctly.

We saw many examples of solutions with projects containing links for the same software with some nuget packages supplied with the solution and others that indicate locations in the path of "program files" that are missing on machines without installing Visual Studio. After you try to create software without installing VS, you can really see how your applications are “stand-alone”.

Before I start listing what you usually need to install, let me point out that MS Build is no longer considered part of the .NET platform, but comes with Visual Studio, but can also be installed separately. See this blog post for more: http://blogs.msdn.com/b/visualstudio/archive/2013/07/24/msbuild-is-now-part-of-visual-studio.aspx

For most assemblies, you must install the following software, for example, if you are creating portable class libraries.

The following directories must be copied:

  • Reference assemblies (must be copied from the computer on which Visual Studio is installed from / to the C: \ Program Files (x86) \ Reference Assemblies directory)
  • Public Assemblies (must be copied from the computer on which Visual Studio is installed, from the / C: \ Program Files (x86) \ Microsoft Visual Studio 12.0 \ Common7 \ IDE \ PublicAssemblies directory

We also use Wix and therefore install the following:

I have a similar kit for testing, however this was not part of the question, so I will leave it!

Hope this helps someone.

Update: March 3, 2017

Microsoft recently responded to a long-term user voice request. Support for .NET Builds without having to use Visual Studio on the server for the Visual Studio requirement to be installed on the build server will be removed.

From the description on the download page, "These build tools allow you to create your own and managed MSBuild-based applications without requiring a Visual Studio IDE." Not yet verified, but after RTM I will review this and provide you with the next update.

There is a blog post that promises these build tools set all the prerequisites and can be used to create applications based on MS Build.

+49
Sep 29 '14 at 13:26
source share

Remember: The easiest way to create your visual studio solutions is to install Visual Studio on the build server. Even Visual Studio Express is often enough.

However, you can make it work without it. But sometimes it’s a lot of work to sort it out. You will need to install the correct SDK for the Windows / .NET platform . You can install several of these SDKs side by side. Now that you are dependent, for example, on A SP.NET MVC 5 or Entity Framework 6, you may need to install additional SDKs so that your application can compile. Downloading this data assumes that you have also installed Visual Studio, but many of their payloads can also be installed separately. This can be quite a hassle.

Personally, I'm tired of trying to figure out which parts of the installers allow that. But this is also due to the fact that Microsoft allows you to install Visual Studio on the build server (TFS) with the same license as your development machine, if you are an MSDN subscriber. Read the Visual Studio documentation documentation for more information .

Using Visual Studio on a build server

If you have one or more licensed users of Visual Studio Ultimate with MSDN, Visual Studio Premium with MSDN, or Visual Studio Professional with MSDN, then you can also install Visual Studio software as part of Team Foundation Server 2013 Build Services. Thus, you do not need to purchase a Visual Studio license to cover the work of Visual Studio on the build server for each person whose actions initiate the build.

If you, like me, would prefer this to change in the future, I suggest you make sure that you heard by sending your request or by voting for the existing Visual Studio Custom Voice .

+14
Jun 30 '14 at 6:09
source share

Here, just grab it quickly.

Your building machine should decompose development tools as much as possible. With that said, and as others have said here, MSBuild can run independently of Visual Studio, and it should be!

If your build requires the launch of Visual Studio, there is a very good chance that you have a problem with the solution or project architecture that needs to be solved.

+5
Jun 01 '15 at 20:02
source share

Visual Studio does not need to be installed. MSBuild is part of SDK.net.

Other .net dependencies should be installed, though, if you use them. MSTest or anything that is part of the Team Foundation will require the installation of Visual Studio.

0
Jun 30 '14 at 7:04
source share

I believe that you only need MSBuild (this is part of the .NET platform that you are aiming for).

Make sure you have installed the correct .NET distribution

following: this is a good place for build servers that have developer tools.

The .NET Framework 4.5.1 developer package installs a multi-targeted package for the .NET Framework 4.5.1. Developers can create applications targeting the .NET Framework 4.5.1 using Visual Studio 2012 or a third-party IDE. You need to download the web installer instead of this package if you intend to redistribute the .NET Framework 4.5.1.

http://www.microsoft.com/en-us/download/details.aspx?id=40772

Good luck.

0
Mar 17 '15 at 12:33
source share

C ++:

There is Build Tools "which contains MSBuild; Visual Studio is not required.

From the white paper:

These tools allow you to create libraries and applications in C ++ targeting the Windows desktop. These are the same tools you'll find in Visual Studio 2015 in the stand-alone installer for scripts. Now you just need to download the tools necessary to create projects in C ++.

Managed:

Same applies: Managed Build Tool

0
Oct 17 '17 at 21:58
source share


More articles:


All Articles