<div>
With continues integration (CI), your team should be checking in code more often so that you get the full benefits of a continues integration platform.<br />
<br />
Also, I would suggest that when moving code to your QA environment that you use the executables that were produced on from the CI system. This is due the the fact that this machine is more likely to have no extra software which also means that you have a better chance of replicating your production environment (on a smaller scale) than if your developers were delivering code executables from their desktop environments.
</div>


With continues integration (CI), your team should be checking in code more often so that you get the full benefits of a continues integration platform.

Also, I would suggest that when moving code to your QA environment that you use the executables that were produced on from the CI system. This is due the the fact that this machine is more likely to have no extra software which also means that you have a better chance of replicating your production environment (on a smaller scale) than if your developers were delivering code executables from their desktop environments.

<div>
<div class="content wysiwyg-content">
Hi experts,<br />
My .NET team has been asked look at Continuous Integration, similar to Hudson (a parallel to CruiseControl). &nbsp;I've come across several articles:<br />
<a href="http://msdn.microsoft.com/msdnmag/issues/06/03/teamsystem/default.aspx#S2" rel="ugc nofollow">http://msdn.microsoft.com/msdnmag/issues/06/03/teamsystem/default.aspx#S2</a><br />
<a href="http://aspnet.4guysfromrolla.com/articles/120104-1.aspx" rel="ugc">http://aspnet.4guysfromrolla.com/articles/120104-1.aspx</a><br />
<a href="http://nant.sourceforge.net/" rel="ugc">http://nant.sourceforge.net/</a><br />
<a href="http://en.csharp-online.net/Unit_Testing_with_NUnit" rel="ugc">http://en.csharp-online.net/Unit_Testing_with_NUnit</a><br />
<br />
But this is totally new to us. &nbsp;Any good recommendations on how to do Continuous Integration for a .NET team?<br />
<br />
Thanks in advance
</div>
</div>


Hi experts,
My .NET team has been asked look at Continuous Integration, similar to Hudson (a parallel to CruiseControl).  I've come across several articles:
http://msdn.microsoft.com/msdnmag/issues/06/03/teamsystem/default.aspx#S2
http://aspnet.4guysfromrolla.com/articles/120104-1.aspx
http://nant.sourceforge.net/
http://en.csharp-online.net/Unit_Testing_with_NUnit

But this is totally new to us.  Any good recommendations on how to do Continuous Integration for a .NET team?

Thanks in advance

How do we do Continuous Integration for a .NET team

Software is any set of instructions that directs a computer to perform specific tasks or operations. Computer software consists of programs, libraries and related non-executable data (such as documentation). Computer software is non-tangible, contrasted with computer hardware, which is the physical component of computers. Software written in a machine language is known as "machine code". However, in practice, software is usually written in high-level programming languages than machine language. High-level languages are translated into machine language using a compiler or interpreter or a combination of the two.

Software

Programming includes both the specifics of the language you’re using, like Visual Basic, .NET, Java and others, but also the best practices in user experience and interfaces and the management of projects, version control and development. Other programming topics are related to web and cloud development and system and hardware programming.