Handling multiple websites

I've been evaluating BuildMaster for the past couple of days and have worked out how to do more or less everything I need to except one fairly major task.

Currently we are using Visual Studio's Publish Web tool which deploys all core website files (over 30 projects), core JS and core CSS files to the website selected. Each website has three publish profiles - dev, test, live.
Each website also has a set of unique assets - CSS, JS, images and templates and these are uploaded separately to a CDN from another Visual Studio solution.

The core website code is common to all websites as is the database structure.

What is the best way to set up BuildMaster to handle this situation?

So far, in BuildMaster I have created an application to hold the core project and a second project for testing the concept of fetching all the components needed to build the website including the core project.

Any help or guidance is definitely appreciated.

Chris

Product: BuildMaster
Version: 4.2.7

The main strategy is to have one application per website, and then either:

Pull the core 30 projects and build them as part of each website application, you can use shared/linked action groups for this to make it a little easier.

-or-

Build the web core files in their own application as you've started to do it seems, and store the build output as an artifact, then import that deployable in each of your website applications. This allows you to deploy the artifact with the core files in it before you build one of your web applications. We've named this option the "Core Version" pattern, and you can find a specific example of it here: http://inedo.com/specifics/buildmaster-extensions

I will also note that deployment plans are getting a nice overhaul in the upcoming BuildMaster v4.3, it will be much simpler to share deployment plans across applications so managing plans for this scenario will be even easier.