I’m designing a Module that is to be consumed by two distinct WebSites. Everything

Question

0

Asked: May 15, 20262026-05-15T22:09:07+00:00 2026-05-15T22:09:07+00:00

I’m designing a Module that is to be consumed by two distinct WebSites. Everything

0

I’m designing a Module that is to be consumed by two distinct WebSites. Everything will be written in MVC (the module and both web applications).

I would like to design my module so that the code can be included from a shared location. I only want to maintain a single version. My first thought was the Area feature of MVC 2. But from my reading it appears as though MVC 2 only “officially” supports Inline Areas.

It sounds like MultiProject support for Areas could be dropped in the near future. What are the pros and cons of Areas implemented as single projects vs multiple projects in asp.net mvc

Are there any alternatives?

A real world example of my design would be creating an MVC Shopping Cart (this would be the shared Module) and consuming it on two different MVC web sites (say a Book Store and a Bicycle Parts Store).