views:

300

answers:

3

What is the best practice for sharing the assemblies of a bin folder across multiple ASP.net websites in IIS 7?

I've got several sites, each with slightly different HTML front ends, but all with the same middle tier logic and DB. I don't want to redploy the same dlls to each of the many site's bin folders everytime I make a change.

Thanks.

+1  A: 

Yes, actually, you do want to deploy them individually. That's how it works.

If this truly offends you, then consider whether this common code should be in a WCF service called by all those sites.

John Saunders
hmm...ya, basically what I have is the same application branded differently across multiple cities...it seems quite redundant to put he exact same dlls inside a new web application for each one of these cities, when the only difference is the HTML views and the CSS.
Scott
As was suggested, you may want to make this one site, but adjust the branding based on the host header and/or user authentication.
John Saunders
+1  A: 

Another option is to make your .Net code smart enough so that it can load the correct HTML front end based on the URL. That way you could deploy your code to one location, then have multiple virtual directories use the same code.

David
That's not a bad idea David. I'm using ASP.NET MVC, so I could just have different Views for each city, and have the city on the URL somewhere, and then I could have one webapp with one controller, just with front end logic to toggle the views.
Scott
A: 

You could possibly try putting them in a common folder location and then change the assembly probing paths to look in that location.

Haacked