Hello all

Can anyone assist me? I have a module that I have been developing in Visual Studio 2008 as a 'Precompiled Module', which I believe is more or less a Web Application Project that builds the ASCX files into a DLL. The solution resides within the DesktopModules folder of the development DNN 5.6 site. I get as far as building, and it works OK, i.e., I can build the DLL to a bin folder, but then I'm not sure what I should be doing.

I'm familiar with creating a module directly from ASCX files using the DNN Module Definitions tab, I've done that successfully enough times before, but I'm pretty sure that this isn't the way to installing the module when it is already a DLL - presumably this is a 'precompiled module', but how do you get DNN to register the module when it is a DLL, as you would do when using the ASCX controls directly?

I'm guessing that it is something to do with either the manifest file, or the location of the bin folder, but can somebody help to point me in the direction for the next stage: at the moment I have a DLL file that I can't get installed into DNN! Does the manifest file somehow get integrated into the DLL during the build, or does it remain outside the DLL ready for another layer of packaging?

Thanks for any suggestions!

Hi

  Thanks but I'm a still too woolly on this, and that URL you suggest seems to have gone now. I'm trying to install my precompiled module into DNN 5.6.0 but it seems the install is failing, though I don't get any error until I try to edit the properties of the module. Anyway, I don't think the install works properly - at the moment I'm letting DNN create the package by pointing the module definitions page module installer at a manifest file that includes the precompiled dll as a  node. Is this a valid approach for installing the module when it is a dll, or is this only for custom dll's to modify the DNN system itself?

A foobar version of the manifest follows. Apart from all the foobars, this is exactly the manifest format I am trying to use:

type="Module"
version="01.00.00">
FooBar.Uploader

FooBar Uploader blah blah blah.


FooBar
FooBar
www.foobar.co.uk
info@foobar.co.uk

05.06.00





bin
FooBar.Uploader.dll






bin
FooBar.Uploader.dll







I don't get any positive confirmation at the end of the package install process, and even though the module name is shown in the definitions list, I can't do anything with regarding editing properties, and the module does not appear in the 'Add module' lists when I edit a page. The Event Viewer in DNN just shows an object not found error when I try to look at the properties, so the module obviously isn't getting installed properly, though I can apparently uninstall OK afterwards.

Where could I be going wrong? Is the manifest obviously incorrect somewhere? Is this not a valid way to install precompiled DLL?

Thanks for any advice about how to troubleshoot this issue.

Regards

Paul,

I can see from what you were able to post of the manifest and from your other comments believe that you are trying to create a module package containing ONLY the assembly (dll) file. To be installed a module, the package must include not only a properly structured manifest and the assembly (.dll file) but also the module controls (.ascx files), any language localization resources (.resx files), and any SqlDataProvider scripts necessary for creating database objects used by the module.

I would suggest looking a several of the simpler DNN 5 module projects in the Forge/CodePlex to see how their packages and manifest are structured. The following CodePlex project by Chris Hammond provides a template for a compiled module which makes use of a MSBuild script to automatically package the module. That approach is similar to my own module development process.

http://christoctemplate.codeplex.com/

Finally, if your module is located in a folder of DesktopModules and is fairly simple in design (in particular only one assembly) and you have already registered its definition and controls in Host-->Extensions or Host-->Module Definitions you should be able to create a basic install package automatically by following these steps:

1. While logged in as host user navigate to Host --> Extensions
2. Click on the edit pencil beside the entry for your custom module.
3. Click on "Create Package" link at the bottom of the page.
4. Leave "Use Existing Manifest" unchecked and "Review Manifest" checked.
5. Click "Next"
6. You will be presented with a list of files found in your modules' folder. It should include the .ascx files, .resx file, other support files and any .SqlDataProvider scripts but will not include the assembly (dll). You can delete from or add files to this list as may be approprate.
7. Click "Next".
8. You will be presented with a list of assembilies based on your modules' Visual Studio project file. If the module's assembly is not listed, type in a path relative to the root folder of the install or if it is in the site's /bin folder, just the assembly name - for example MyModuleAssembly.dll.
9. Click "Next"
10. A manifest will be created and you will have the opportunity to edit it.
11. Click "Next"
12. Leave "Create Manifest" checked and if necessary edit the manifest file name. Leave "Create Package" checked and if necessary edit the package file name.
13. Click "Next"
14. The completed package (.zip) will be placed in the site's Install/Module/ folder.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner