the source version is the full source, except for external dependencies e.g. telerik, clientAPI, ddrmenu as we only use the compiled assemblies. We don't have a single project where these exist in code form (we couldn't with telerik as we'd dont have their source). Regarding clientAPI, it's a long deprecated part that only still exists due to the number of modules/skins that have dependencies on it - in the past when we've had to make fixes we make them at the codeplex site and then add the updated dll's to DNN, but ideally we'd like to stop using it altogether so it's unlikely to ever be added as source to our solutions. DDRmenu is different as it's actively used, and we are considering brining into it the source tree (as long as Mark doesn't mind).

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

ClientAPI is a dnn class, but it uses the dotnetnuke.webutility dll (which in turn uses the dotnetnuke.webcontrols.dll) - both of those are external projects which have not been updated since 2011. We investigated removing these dll's and pointing the clientAPI methods to some alternative, but it turned out to not be trivial - we may end up finding a solution for it in the future but there it isn't something we're looking at in the near term. As neither dll has been updated since 2011, it means that they're effectively deprecated i.e. users should not expect any future enhancements. Unfortunately, the .net framework doesn't have an attribute to declare that something is no longer being developed. That said, there's very little reason nowadays to use clientAPI -instead MS Ajax or the service framework (when used with javacript/jquery) can do anything it does.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US