What puts SharePoint on the top of the list?
Picking A DNN Version
Your choice of an appropriate DNN version is one of the most important of all DNN system requirements, and should not be skipped. As a DNN developer trying to configure a DNN environment for yourself, you need to consider picking a particular DNN version before you start developing.
You only want to develop on your suitable version like what you have got in production which will enable you to know what DNN version you will need to configure as your development environment. Developing on a newer version than what you have currently can cause specific compatibility issues in the long run.
This rule is also applicable when configuring a DNN environment for commercial purposes. You should be able to strike a proper balance for your potential customers. From a developer’s view, you can decide to develop on newer versions, but in my informed opinion, it is advisable to create on older versions. This is because not everyone upgrades their DNN CMS as often as expected hence providing support for customers on all versions of DNN.
Another thing you may like to consider is feature updates. Some features may be made available only on newer updates of DNN, like workflow functionality which became a staple with DNN 5.1.
Providing support for this DNN version feature will inevitably leave older versions out of the loop which inherently would not be your fault.
This phase tends to be a tricky one. As part of the DNN system requirements, you will want to pick the “install” package over the “source” package. This choice is because you do not require the source package, although you can still use it if you wish.
Using source install makes thing a bit cumbersome, and since we won’t have to launch the DNN project, there is no need having the file settings sitting around without usage.