title: Prism with ASP.NET
body: <p>My company is looking into ASP.NET and Prism.  We are wondering how much code reuse we can get between the two options.</p>
  
  <p>As I see it Prism has these "parts":</p>
  
  <ul>
  <li>Shell (Bootstrapper and such)</li>
  <li>Modules</li>
  <li>Services (not web-services)</li>
  <li>Regions</li>
  <li>Loosely Coupled Events (IEventAggregator)</li>
  <li>Unity (though really this is a standalone product)</li>
  </ul>
  
  <p>As I look at this, the only part that absolutely must be used with Silverlight/WPF is Regions.  </p>
  
  <p>The shell may be a bit tricky, but I think It could be done in an ASP.NET app.  I also think that Modules (non-Region offering modules) should also be doable.  Using IEventAggregator and Unity should be easy.</p>
  
  <p>The only problem I have is that I am not really experienced in ASP.NET programming, so I am not sure of my assumptions.  I would love some feed back from someone who is familiar with both Prism and ASP.NET before the discussion on this goes into full swing (here at my company), .</p>
  
  <p>Basically, I want to make Prism modules that will run web-services and business logic.  I then want to take these modules and (re)use them in ASP.NET apps and WPF/Silverlight Prism Modules (via Regions).</p>
  
  <p>Am I charting a difficult journey by trying to merge these two systems?</p>