The architecture of the Web Framework here is mostly solidified around existing products - some open-source and some purchased.  DNN has continued to live up to our expectations in terms of flexibility and robustness.  We renewed our service contract with AspDotNetStoreFront in order to get the beta bits for the DNN Storefront product.  Right from the start I was seriously disappointed with the readiness of the product for beta release and have currently revised the storefront to use dashCommerce - the current incarnation of the Commerce Starter Kit.

dashCommerce is exactly what I'd hoped for in terms of structure and integration with DNN was fairly straightforward as far as the user authentication and profile management bits go.  There were a few bugs that I found annoying (the order entry email was sent to the customer rather than the configured address) for a v2.x project, but the overall structure of the project is solid.  Right away I was able to use the UPS shipping and rating module and the Authorize.Net module with just a bit of tweaking (the configuration values for Authorize.Net don't 'stick' from the UI and had to be entered manually in web.config).  Also, for a web commerce project to be lacking friendly URL rewriting I was disappointed, but there were some excellent posts in the user forum concerning integrating the Intelligencia URL rewriter with dashCommerce and this was accomplished with little difficulty and works well.

As far as I can tell the DNN Store :: Module from Will Morgenweck has still not passed the DNN release process yet and there's no firm commitment from the team as to a target date.  Anyone have an update on this, let me know.

An unplanned event provided us the opportunity to launch a site on the Web Framework (http://www.leadtesttoys.com/) and put it to the test.  After two-weeks of shakedown I'm pleased overall with the flexibility and performance of what we have and have identified a few items which need to be adjusted before we go live with the additional sites:

• Integrate the Engage Publish CMS tool with dashCommerce or improve the manageability of the dashCommerce Paragraph user control
• Eliminate content contained in html or aspx source files
• Create a strategy for streamlining the process of creating SKIN files for DNN and THEME files for dashCommerce - any ideas here?

Following is a view of the high-level components which currently comprise the Web Framework: