asp.net - .NET automated build with cruisecontrol.net + nant - multiple assembly structure / best practice -

I am doing some work with many shared .NET assemblies and a normal web application that handle me better Would like to cc .NET / NNT build environment.

At present, we have several .NET assemblies (shared common codes which we use in client projects) which are separate within different repositories in our SCM. ). They are configured separately under all CC.NET, so we currently have a decent control over their construction and deployment.

We have developed the CMS system which uses some .NET assemblies and has a general administration website project and a template website example project in it. In this one solution we have the following elements that need to be managed separately:

• The admin interface is not connected to .NET, so this template is based and we are currently A PHP backend is developing.
• Build our own CMS Shared Assembly Build Up on Comprehensive Assembly.
• Control the functionality within each major CMS build / release.

I want to see the output of this solution to be a visual studio template, which we have to develop other client sites and better manage version variations within CMS Because we add features to the codebase.

I have a rough view for all of this and it seems that this is possible, however, I wanted to open this topic for discussion and want to see that there are many solutions to manage and manage the deployment What are these for?

The main reasons for us are:

• Do we use the unity queue functionality in CC.NET so that a build order is ensured. Need Assemblies?
• Debugging within the CMS client site i.e. stepping into the code of shared assemblies when the customer solution base is a version of the CMS system and therefore is different. / Li>
• Developing and extending CMS when it uses shared assemblies i.e. we add assembly projects to the trunk solution during development (in Source Control Treasury) and then to construct it together to pull it together Trust or do we use it completely different approach?
• Can any other problem be experienced which can change the way we think?

Hope this question is not very ambiguous and some of you have worked with these issues to look forward to hearing all the experiences.

Many thanks! Tim

I can not unfortunately answer all of your points, but start with me here:

• Do we use the Unity Queue functionality in CC.NET to ensure a build order and to build assemblies necessary for CMS together at the time of construction?

The short answer is yes, you must have a build order within the example of the queue attribute running CC.NET and ensures that you build on each other Gives the serialization to specify which projects are dependent on one another, you should use not rely on the queue priority for this task.

You are most likely that you will pull the necessary pieces to build on build times. Unless there is a shortage of time on your personal construction.

• Developing and extending CMS when it uses shared assemblies i.e. we add assembly projects during the development of the trunk solution For (in Source Control Treasury) and then rely on the construction to pull it together or do we use a totally different approach?

Unless I distribute binaries in the trunk as long as they are not some libraries that do not need to be constantly updated if you have shared assemblies , You should consider pulling them with artwork on Build Server.