Hi All,

 I work for a company as an in-house developer and would like to know what the minimum requirements are for plugging in a module.

The cristocs template are of course excellent, but as an in-house developer I am not creating modules for anyone except the company. Using a template, there seems to be so much to consider; manifest files, installation packages, dataproviders etc.

I will have direct access to the database so can make changes with SQLServer Management Studio and ftp access to upload any files; dll's, css svc files etc.

 So I have a lot of bespoke functionality requirements and need to make many modules. I feel like it is quicker to just create UserControls that inherit from the PortalModuleBase and ftp them to DesktopModules folder. With that in mind, what are the minimum requirements for module development, registering a module with the website and including a module on a page.

 Thank you for your time with this.

Mike,

The new Module Creator tool in dnn 7.2 is a great way to start - you can go - "Create New Module" on any page - and it will generate a fully functional ready to go module registered on you page with all the manifest stuff handled for you and a general a module framework ready to go that you can then start editing inline or you can open the website up in visual studio and edit the files that way as well.

Alternatively - you can create the file structures yourself in Visual Studio and use the Extensions manager to Create a new module definition registration.  

Westa