Ezequiel Jadib’s Blog

Some time ago, I wrote about a new WCSF sample application we had published in WCSF Contrib. 

Now I’m writing again about this application because we’ve just published three new articles that describe the work done in each of the modules.

If you are interested in this sample, you will find the new articles very useful.

Articles

• Kick off
• Product Module - NEW!
• User Module - NEW!
• Admin Module - NEW!

Download E-Commerce Catalog

Enjoy!

I’m happy to announce that we have just published in WCSF Contrib a sample application developed with Web Client Software Factory 2.0.

The application is an "E-Commerce Catalog" and is intended to:

• Show recommended practices in incremental Web development.
• Demonstrate how a WC-SF project can be faced and developed.
• Demonstrate how Web Client Software Factory 2.0 assets help to solve common technical challenges.

I recommend you to read the kick-off article in where you will find:

• How the application was designed incrementally.
• The rationale behind our technical decisions and implementations.

These are some of the technical challenges that the E-Commerce Catalog application addresses:

• Modularity
• Unit testing Web Solutions
• Authentication
• Authorization

You can find more about the technical challenges in the kick-off article.

I hope you find this new sample useful. Any feedback will be appreciated.

And stay tuned!. More articles will be published soon.

Download

After got valuable feedback of the community, we decided to change some things of the previous version.

In this new version we can define the scope of the service we are registering, allowing thus register global and module services. This version is a replacement of the previous one.

Here are the breaking changes:

• Remove the services section from the config file (We added this section in the previous version).
• Change the modules section:

  Change this:

<sectionGroup name=”compositeWeb”>
    <section name=”modules”
             type=”Microsoft.Practices.CompositeWeb.Configuration.ModulesConfigurationSection,
             Microsoft.Practices.CompositeWeb”/>
   <!– Other config sections here –>
</sectionGroup>

To this:

<sectionGroup name=”compositeWeb”>
    <section name=”modules”
             type=”CompositeWeb.Extensions.Configuration.CustomModulesConfigurationSection,
             CompositeWeb.Extensions”/>
    <!– Other config sections here –>
</sectionGroup> 

• Changed the way of how register the services in the config files. Now we have to put the services node into the module node:

  <module name=”Customers” assemblyName=”ModuleQuickstart.Customers” virtualPath=”~/Customers”>
      <services>
          <service registerAs=”MyInterfaces.IService1, MyInterfaces”
                         type=”MyImplementations.Service1, MyImplementations”/>
          <service registerAs=”MyInterfaces.IService2, MyInterfaces” scope=”Global”
                         type=”MyImplementations.Service2, MyImplementations”/>
          <service registerAs=”MyInterfaces.IService3, MyInterfaces” scope=”Module”
                         type=”MyImplementations.Service3, MyImplementations”/>
       </services>
  </module> 
  

Note: By default the services are registered as global services.

• Change the Global.asax file to inherits from CompositeWeb.Extensions.ExtendedWebClientApplication

<%@ Application Language=”C#” Inherits=”CompositeWeb.Extensions.ExtendedWebClientApplication” %>

Source code

• You can get the source code of the CompositeWeb.Extensions project by downloading the WCSF Extensions v1.0 release located at the new Codeplex WCSF Extensions project. If you face problems building the solution, make sure the references to the assemblies are correct.
• Important: The code is provided “as is” without warranty of any kind.