This project has moved and is read-only. For the latest updates, please go here.

Composite Web Client Guidance

Apr 10, 2012 at 7:34 AM

Good day,

I was wondering if you could perhaps help me,

I was reading the guidance associated with the following: Composite Web Guidance

I was reading through the section titled "Define the Solution Structure for a Modular Web Application", particularily the section "Multiple-Project Modules". I seem to understand the basic concepts surrounding this, however I can't seem to figure out a reasonable way to allow this to work with my web forms in seperate projects.

I realise design time support for masterpages will not be supported here, my question however is how to use something like MEF(or another container) to allow me to deploy my projects (which include web form pages and code behind files) as completely independent into a folder and plug them into a solution, the guidance seems a bit unclear as to how to support this and whenever I attempt to import these modules I get run time errors. I've had this working successfully with MVC by exporting the controllers. I would appreciate your support, however I realise that you are an extremely busy people. If you could perhaps link me to a blog or a resource explaining this in detail I would be forever greatful. Thank you for taking the time to read this. To summarise I wish to achieve the following.

  1. Create my web shell project using web forms (without silverlight or any client technology)
  2. Create my modules which exist inside their own projects, which contain my aspx and aspx code behing pages as well as any dependent assemblies
  3. I wish these pages to be exportable and importable by my shell.
  4. If possible I'd like my module assemblies to be within their own folders as to not muddy my solution.