1

I am currently working on ms build to publish my winform application based on the environment selected (Dev or Prod). I am using Ms Build Community Task and referencing this article to achieve this purpose.

I had a few theoretical doubts based on publishing application.

1) Is there any difference in publishing through the visual studio ide and msbuild?

2) What do most developers prefer to use and why?

3) What are the advantages of using MsBuild to publish an application as compared to publishing through the visual studio IDE?

4) What is faster?

I am using a .net 3.5 winform application developed in Csharp and my question is pertaining to clickonce windows applications only. Please help me clear these doubts

Improve this question
2
  • Can you include a link to the article? Commented Mar 18, 2011 at 13:40
  • I have updated the link. wallism.wordpress.com/2009/12/21/… Commented Mar 18, 2011 at 13:42

3 Answers 3

Reset to default
2 
 > 3) What are the advantages of using MsBuild to publish > an application as compared to publishing through the visual studio IDE?

You can run msbuild for Continuous_integration on a dedicated build-server. No need to install Visual studio there (and no licence costs). The free dotnet-sdk (including msbuild) is enough.

Improve this answer
3

I believe the later versions of Visual Studio use MSBuild as the compilation back end. In any case it is a good idea to learn the automated building tools and their configurations so you can achieve a one step build process, for robust testing and stress-free releasing.

Improve this answer
0
1

I actually do something like this in deploying asp.net web applications. Learning MSBuild is a good thing to do because it expands your toolbox. More automation means fewer mistakes.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.