OK.  Let me be clear.  The DNN version of AspDotNetStorefront is a commercial product that will be sold by a third party vendor.  Just like PortalStore and Catalook.  That company has hired TAG Software to assist in performing the conversion effort.  You can find more information about that product at http://www.aspdotnetstorefront.com .

So what does this have to do with the DNN Store module?  Nothing.  The DNN Store module was created to address a specific set of requirements/use cases.  Over time, Rob and his team will enhance the DNN Store to meet a larger and larger set of requirements and to address specific requests from the community.  The DNN Store module will succeed or fail based on the teams ability to continue developing the module and meeting their community's needs.

Right now the DNN Store does not contain all of the functionality required for the DotNetNuke Marketplace.  We had to make a business decision, just like every other company.  That does not mean that the DNN Store is not a good fit for other customers.  Each user who is looking for an eCommerce solution has to do their own evaluation based on their own requirements to determine what is the best solution for their specific set of circumstances.

Does anyone think that DNN Store, in its present form, could run Amazon.com?  No.  DNN Store must build it's community just like DotNetNuke built the DNN community.  When DotNetNuke was first released, it could not have handled the current DotNetNuke.com site.  It wouldn't scale to our level.  It didn't support skinning. It didn't have the same membership and roles capabilities.  It didn't support search, or logging or scheduling.  These features were added over time.  As new features were added, DotNetNuke was able to handle larger and larger websites.  Large enterprises were able to shift their web sites over to run on DotNetNuke.  This did not happen overnight, and it did not happen with version 1.0.  DNN Store, and virtually every other DotNetNuke module, is in the same position.  They are each projects unto themselves.  They must identify community requirements and continue to extend their projects and their communities.  Over time, DNN Store may grow to the point where it can handle larger eCommerce sites.  Part of the way that it will happen, is that people will decide that the current base is a good starting point and will offer to help the team extend the module.  Maybe one of those people is you Rocky.  Maybe not.

When we first launched the DNN Forums, we shifted our internal communications to DotNetNuke.com.  We slowly added more and more forums until we were ready to move the entire community.  This necessarily required a lot of effort by the forums team to implement needed features, provide stability, and deal with scalability requirements.  This was a lot of pressure to put on that team.  It was not very smart on our part, since all of these teams are volunteer efforts.  Teams need to determine for themselves how much time and effort they can afford to spend and adding additional business requirements from DNN only leads to increased stress and frustration for everyone involved.