R – ASP.NET MVC and Service Oriented Architecture

Architectureasp.net-mvcwcf

I would like to know how do i incorporate a feature like wcf within and MVC application. My current idea of the architecture is as follows:

EntityFramework -> ASP.NET MVC (Views)

EntityFramework -> ASP.NET MVC with
WCF endpoints -> mobile Apps.

EntityFramework -> ASP.NET MVC ->
Silverlight (using .NET RIA Services).

So I'd have 1 asp.net mvc project. create my DAL in the models folder. have my controller access that DAL. Add a wcf file somewhere and have that call to the DAL. Some parts of the application i have a silverlight app that opens and uses the asp.net membership information and other related data.

Please correct me. I have no idea what I'm doing.

Best Answer

For your situation, I would do things a little differently.

I would create a seperate project for your Data Access Layer. I would also move business logic into a Business Logic Layer.

You could then share both your DAL and BLL between the ASP.NET MVC site (your Models would be a Facade to the BLL objects) and your WCF Services thus centralizing all of your logic into a central location.

Related Solutions

Asp.net-mvc – Compile Views in ASP.NET MVC

From the readme word doc for RC1 (not indexed by google)

ASP.NET Compiler Post-Build Step

Currently, errors within a view file are not detected until run time. To let you detect these errors at compile time, ASP.NET MVC projects now include an MvcBuildViews property, which is disabled by default. To enable this property, open the project file and set the MvcBuildViews property to true, as shown in the following example:

<Project ToolsVersion="3.5" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <MvcBuildViews>true</MvcBuildViews>
  </PropertyGroup>

Note Enabling this feature adds some overhead to the build time.

You can update projects that were created with previous releases of MVC to include build-time validation of views by performing the following steps:

Open the project file in a text editor.
Add the following element under the top-most <PropertyGroup> element: <MvcBuildViews>true</MvcBuildViews>
At the end of the project file, uncomment the <Target Name="AfterBuild"> element and modify it to match the following:

<Target Name="AfterBuild" Condition="'$(MvcBuildViews)'=='true'">
    <AspNetCompiler VirtualPath="temp" PhysicalPath="$(ProjectDir)\..\$(ProjectName)" />
</Target>

Asp.net-mvc – asp.net mvc put controllers into a separate project

First of all, it is certainly a good idea to put your model into a separate project. As you've discovered, this is trivial.

Regarding Controllers and Views, I don't see any obvious advantage to separating them for most basic projects, although you may have a particular need to do so in a particular application.

If you do choose to do this, then you will need to tell the framework how to find your controllers. The basic way to do this is by supplying your own ControllerFactory. You can take a look at the source code for the DefaultControllerFactory to get an idea for how this is done. Subtyping this class and overriding the GetControllerType(string controllerName) method may be enough to accomplish what you're asking.

Once you've created your own custom ControllerFactory, you add the following line to Application_Start in global.asax to tell the framework where to find it:

ControllerBuilder.Current.SetControllerFactory(new MyControllerFactory());

Update: Read this post and the posts it links to for more info. See also Phil Haack's comment on that post about:

ControllerBuilder.Current.DefaultNamespaces.Add(
    "ExternalAssembly.Controllers");

...which is not a complete solution, but possibly good enough for simple cases.

Best Answer

Related Solutions

Asp.net-mvc – Compile Views in ASP.NET MVC

Asp.net-mvc – asp.net mvc put controllers into a separate project

Related Topic