I have a module that uses the Telerik ASP.NET controls that that is compiled against DNN4.9.2. I want to create a single installation package that can be used for both DNN5 and DNN5 sites.
The Telerik controls were first bundled with DNN5.2.0, so to support earlier versions, I need to include the Telerik dll in my package. I plan to include the same version that shipped with DNN5.2.
I want the installer package to ignore the telerik dll when installing on 5.2.0 or later, so that the module uses the version shipped with DNN. I understand from reading Bruce Chapman's
blog that you can use two manifest files in one package, with extensions .dnn and .dnn5. DNN5 will apparently use the .dnn5 manifest, while earlier versions use the .dnn file. That means I can exclude the telerik dll for installations on DNN5.x sites.
However, what about versions 5.0 - 5.1.x which do not have the telerik controls bundled? Using this technique outlined above, the telerik dll will not be installed and the module will fail.
Is there a way of using the version 3 manifest to conditionally install files, based on DNN version?
Alternatively, what would happen if my installer simply tried to install the telerik dll, regardless of whether it is already present? Would it overwrite it, or would it skip the copy if the file was already present?