Hello:
I would like to start this post by saying how much I like the code (that there is) for the Core Store module. As I noted in previous posts, I am continually delighted with the elegant solutions to problems I had when developing my own module. When the core store module was released with DotNetNuke, my module on SnowCovered sold as a fixer-upper stopped selling. What killed my continued development (other than the inclusion of this incomplete module in the core) was figuring out how best to store provider specific configuration data. Unlike the CommerceStarterKit, which uses configuration files for storing and configuring most of it's providers, a DotNetNuke module must be able to store settings for any number of stores in it's module settings, which was a hurdle I couldn't get over in my 4-10 hours a week I could allocate to continued development. I originally gave away the module for free on my site for several years and will most likely continue to do so once I get permission from my ex-partner.
Other design features of this module I really like include how it separates each of the various features/layers into separate assemblies. In my own module, I had several UI layer modules and a Core Business Logic layer, which had it's own data provider. That way I could add new UI Modules referencing my business layer without having to modify any code, just as the current architecture. That being said, I have no complaints about the current structure other than it appears to have gotten too complex for a programmer donating 4-10 hours per week to the project who also has a wife, kids, and occasionally wants to do something other than sit behind a terminal and code.
The big issue is: I have seen several developers volunteer in recent months to help resurrect and contribute to the module, and we have gotten spotty and somewhat ambiguous updates along with polite acknowledgement that when the major .net 2.0 changes are checked in, development can move forward. It has been several (read more than three) months since this was announced and have received little if any news of progress. We did receive news as recently as early as 11/14/06, Robert Collins wrote in the thread "How to use Store module?":
"We are trying to get a new, much more stable/feature rich version out the door. We had a developer go MIA so as soon as we get their code checked in we will test and release."
Which leads one to question: Does this mean the source is in his possession and all he needs to do is check it in, or, they can't find the developer and therefore can't find the source the developer was working on therefore there is no determinate date for getting this thing out the door. My vote is: if we can't get the code checked in by next Friday, then check in what you have, and release this to the community as an alpha. As you stated, the module is in source control... does this mean that the source control system being used does not integrate with Visual Studio? Can this project have it's code hosted on a site such as CodePlex that offers source control integration with Visual Studio for open source projects? It is just a little frustrating (as many others have pointed out) that such a promising project has lay stagnant for so long with so much possible community support. As noted previously in this forum, ideally the project will not rely on any one person or secret group to get what needs to be done accomplished. I do understand that the migration to ASP.NET 2.0 technologies required many architectural changes which has substantially delayed development, but there should be a limit to holding out for these changes: if this person can't contribute back to the project, forget about him, and let someone else do it (damn it!). Lets just get this project moving!
I hereby volunteer to put my money where my foot is, and will happily contribute several hours (or more) a week to this project. I bring twelve years of solid development experience in multitude of projects which includes nearly four years of that time in .NET framework development. About 75% of my last eight years has revolved around Internet development, first with the IIS 1.0 IDC, then Classic ASP in 1998, and then ASP.NET in 2002. I have been a DotNetNuke enthusiast since discovering it with the introduction of version 2.0 and have developed tens of modules for as many customers. I currently work as a senior developer with the largest privately owned online university company in the world where I primarily work on a sophisticated sales application based loosely upon an early fork of the .netTiers framework. Most relevant, I have implemented this module on my client's site and would like to be able to offer back to the community some of the many modifications I have made or will have to make for his site to be fully functional.