There is probably 20 different ways to do this but I'm going to post my requirements and see if there isn't a .NET developer out there that could give me some advice.

I've got a dedicated webserver that has about 350 websites using an old ASP style proprietary framework for content management. To access my standard code base I had a directory called 'framework' that i tied in as a virtual directory on each of the 350 sites. The code is "included" at the top of every page using the include command. This way my code stays in one place and any changes to that code are immediately Now moving to .NET I want to setup my architecture so it's easy to manage the framework.

So I'm expecting I will have a data layer and a business object layer that I'm going to want to be in a central location. Most likely I will also want a centralized base presentation layer I can extend and subclass on specific sites if required. I'm also intending to include a lightweight set of pages that can run my new ASP.NET modules inside the existing websites using Iframes. This will help me in moving more quickly 350+ web sites to use my .NET components without breaking everything and starting from scratch I will reference these in my individual webpages.

Now I guess my question is how can I pull this off so I can have an easy to manage development cycle for debugging and testing and that I don't have to generate 350 dll's each time I make a code change? Maybe I'm trying to make it harder than it needs to be but right now I'm just not finding the 'clean' way to share codes across sites. Within an ASP.NET project it seems there is much flexibility but once I start wanting to use code across sites the testing and development cycle seems elusive. Any help or advice will be very much appreciated.