I am working on overhauling a DNN website.

The old website is DNN6, and the new one is DNN7.

Our old DNN6 site has several custom-made modules that a previous employee had developed.

I would like to move these modules from the old site so they can be used on the new site. (*IF* they work with DNN7... I'm not sure if they will, but I want to try.)

I have tried moving the module from the desktopmodules folder on the old site to the new site's desktopmodules, but they don't show up in DNN when I go to add a new module.

I'm sure I'm missing some step required to "register" the new module, but I'm just not sure how to do that.

Thanks!

If you go to Host, Extensions and edit the module (pencil icon to the right of then entry) you will find a "Create Package" link at the bottom of the page or popup. Use that to create an installable version of the module. You should then be able to install that file in your new installation using the stardard Install Extension Wizard.

Hopefully, the former employee left behind source code and, perhaps, and install file for the modules?

The good news is that a DNN 6 module should work with DNN 7, provided that the module was written with "good" programming practices.

If the module doesn't work and you don't have source code, it's going to be a tougher step, but not an impossible one.

I don't know if there are install files.

In the folder current module I'm looking at, there are three files:
rcu_plc_onlinecourse.ascx
rcu_plc_onlinecourse.ascx.cs
rcu_plc_onlinecourse.ascx.org

None of these modules show up anywhere on the Extensions page.

I think that you'll need to learn how to package and install DNN modules. Hopefully, you can get your developer to figure this out and you should insist that you have installable modules!

On way to start would be to ask the developer to use the "Cristoc" module template from Codeplex.com. That can be downloaded for free, and it's probably a quite simple task to download the existing module files and incorporate them. You probably have at least one .dll file in the bin directory, too. Your developer should provide you with both Source and Install versions of the modules. The template makes it easy to do that.