MSBuild
-
Hi All, I am pretty new in terms of MSBuild, so please dont humilate my naive questions :-) Can someone plz tell me what's the benefit to use MSBuild and why we need it. we can create a porject in M/S visual studio and then build the project in the M/S visual studio. I dont know why we need this tool(M/S Build)? Many thanks
-
Hi All, I am pretty new in terms of MSBuild, so please dont humilate my naive questions :-) Can someone plz tell me what's the benefit to use MSBuild and why we need it. we can create a porject in M/S visual studio and then build the project in the M/S visual studio. I dont know why we need this tool(M/S Build)? Many thanks
Tasks such as creating installs, updating version numbers, creating escrows, distributing the final packages, etc. can be automated and made easier with what MSBuild (or Nant) provide. The dev env just does a build.
There are only 10 types of people in this world — those who understand binary, and those who don't.
-
Tasks such as creating installs, updating version numbers, creating escrows, distributing the final packages, etc. can be automated and made easier with what MSBuild (or Nant) provide. The dev env just does a build.
There are only 10 types of people in this world — those who understand binary, and those who don't.
-
Hi All, I am pretty new in terms of MSBuild, so please dont humilate my naive questions :-) Can someone plz tell me what's the benefit to use MSBuild and why we need it. we can create a porject in M/S visual studio and then build the project in the M/S visual studio. I dont know why we need this tool(M/S Build)? Many thanks
In addition to the clever build tasks mentioned already MSBuild is the engine used by Team Foundation Server to perform automated builds. In fact even building a solution in Visual Studio is using MSBuild. VS just autogenerates the MSBuild script on the fly. So the advantage of using MSBuild is that you can build .Net applications. Since the release of .Net 2.0 there has been no other way. (I believe Nant just calls VS to perform the actual build, which in turn calls MSBuild). Because of this, extending the build process to build multiple projects and perform extra tasks is mostly a matter of adding to an xml file, though more specialised tasks may require a custom build task to be written in .Net.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
-
In addition to the clever build tasks mentioned already MSBuild is the engine used by Team Foundation Server to perform automated builds. In fact even building a solution in Visual Studio is using MSBuild. VS just autogenerates the MSBuild script on the fly. So the advantage of using MSBuild is that you can build .Net applications. Since the release of .Net 2.0 there has been no other way. (I believe Nant just calls VS to perform the actual build, which in turn calls MSBuild). Because of this, extending the build process to build multiple projects and perform extra tasks is mostly a matter of adding to an xml file, though more specialised tasks may require a custom build task to be written in .Net.
If you have knowledge, let others light their candles at it. Margaret Fuller (1810 - 1850) [My Articles] [My Website]
-
Thanks very much, can you please offer me an example that does all of or some of those tasks?