JustTrying wrote
leupold wrote
Please notice as well, that source version of DotNetNuke 3.3.0 and 4.3.0 does not include source versions of modules. You will need to download and install source code versions of modules separately from the projects' download page.
|
1. Could we get a reason for why the source code for the modules is not in the source version of DotNetNuke 3.3.0 and 4.3.0? Just asking.
2. When will the updated source the modules be available?
3. Will there be a place where we can download all modules sources at once for either 3.3 or 4.3? It is very time consuming to go through each module project and download each source.
I am developer going to start a new project and would like to start with the entire source for the project and build from that. If all or some the modules have been updated with improvement I would like to start from there and use those as example for building new modules and enhancements.
Thank you,
Jeff
Each module is a separate sub project and maintained by a separate team of volunteers. To integrate the source of these modules would further (and unnecessarily) strain the developers who put a great deal of time and effort into this release. I have been waiting I can't tell you how long for this great release, and ANYTHING to expedite that process is surely worth a few extra minutes to download the source versions of the modules! As it stands, I believe this is the first major release to automatically install the 'uber' DotNetNuke modules: Forums, Gallery, Blog, Repository, and Store. It is such a trivial thing to download and install the source for these modules, I can't believe anyone would bother griping about it as it would probably take less time to download and install the source than to write the actual complaint!
That being said, I am simply amazed by this release! Thanks to everyone who worked on this! With the introduction of the old, closed source Microsoft written Membership provider, I had essentially lost faith in DotNetNuke for what I use it for: School, Church, and club web sites. Touted as DotNetNuke's original 'killer app' feature, DNN's ability to host multiple portals was terribly hobbled by the earlier 3.x membership provider because users were not unique to the system, just to portals. So if a user decided to change her password in a subportal, that change would not be reflected in her root portal profile, without the use of one of the less than optimal third party solutions. Tack on to that a cryptic, non-standard method of storing user profile data in a text/blog field such that it was nearly impossible to work with, and DotNetNuke became all but off limits for anything but simple, one-off basic web sites.
Again, thanks to all who toiled long hours on this release, it has brought a great deal of joy to this developer.