Nant is the most commonly used one. But if you are using TFS, you should already have that capability built into the server.
With NAnt, you can configure everything that you have mentioned above with the little extra coding.
Use [code]your code here[/code] tags when you post source code
Search here before you post your question, someone might have already asked it before. My Articles
ugh, just the word nant makes me want to sever my jugular w/ a dull spoon. brings back difficult times hand writing nant scripts.
I would rather use MSBuild anyday (especially with the built in support for custom actions via C#). it just uses your solution files for building and you can schedule tasks in the task mgr for it (and it will run automated tests you have included, and should be able to send emails as well).
we use visual build pro which works rather well and can do anything you can think of (and lots of things you can't). we use it to get latest, build, run msi's for merge modules, and installers, and copy things out to distribution channels. we could run tests in there too if we wanted.
hmm... I could not understand what you people are talking about. if these are build machines then why is microsoft .NET studio used for building C# source code ??
You misunderstand the role of msbuild. Visual Studio uses msbuild to compile projects, not the other way round. msbuild is a commandline utility which can process .sln/.csproj files and compile them.
NOTE: My code snippets are just snippets. They demonstrate an idea which can be adapted by you to solve your problem. They are not 100% complete and fully functional solutions equipped with error handling.
ugh, just the word nant makes me want to sever my jugular w/ a dull spoon. brings back difficult times hand writing nant scripts.
I would rather use MSBuild anyday (especially with the built in support for custom actions via C#). it just uses your solution files for building and you can schedule tasks in the task mgr for it (and it will run automated tests you have included, and should be able to send emails as well).
we use visual build pro which works rather well and can do anything you can think of (and lots of things you can't). we use it to get latest, build, run msi's for merge modules, and installers, and copy things out to distribution channels. we could run tests in there too if we wanted.
I would second that
Use [code]your code here[/code] tags when you post source code
Search here before you post your question, someone might have already asked it before. My Articles
Any good Build Machines for C# projects?
Reply With Quote
Re: Any good Build Machines for C# projects?
Originally Posted by MadHatter
Re: Any good Build Machines for C# projects?
Bookmarks