Import Module Manifest

[email protected] · January 18th, 2010, 10:51 PM

Chapter 9 Page 146 show the Module Definition action menu opened (Figure 9-1: Selecting Import Module Definition from the action menu)

the "Import Module Definition" item is Highlited .

I'm use DNN 5.2.1 Community version

This option is not available on my "Module Definition" action menu .

Can anyone help?

Thanks
Dexter

msellers · January 22nd, 2010, 04:26 PM

You should have this option from Module Definitions, I just validated this on a local 5.2.0 installation.

shirk99 · January 29th, 2010, 11:13 AM

I also have community edition 05.02.01 (54) and do not have the option to import a module definition. I can provide screenshots if helpful.

shirk99 · February 1st, 2010, 12:28 PM

Mitchel, I upgraded my dnn from 5.2.1 to the latest 5.2.2 just to make sure I'm using current software and not wasting your time. Will you take a look below and compare this with your own findings?

I saw in one of the forums that DNN has changed the way you add modules. Here is how I'm attempting to do this, since page 146 is no longer viable.

Host => Module Definitions
From dropdown menu, 'Create New Module'
Create Module From: Manifest
Owner Folder: <Not Specified>
Module Folder: GuestbookVB
Resource: GuestbookVB.dnn
Add Test Page? Unchecked
CLICK Create Module

Ok, after clicking the Create Module button, the screen reloads, but looks exactly the same. No confirmation, no errors. (If you try clicking it again, same thing.)

Now, despite the fact that it looks like nothing happened, go ahead and click on the link for "Module Definitions". Scroll to the bottom, and the module is listed there. This is where I stopped with the book's instructions - I want to make sure I'm using the proper steps (and hoping to yank a comment out of you confirming that this new dnn functionality has a bug in it).

I clicked the red X to uninstall the module and chose to NOT delete the files. I get a few errors. Below is a copy and paste of the uninstall log. My comments end here - the rest of this post is the pasting.

Package Uninstall Logs

Info Reading Component Manifest - Script
Info Reading Component Manifest - Module
Info Module Manifest read successfully
Info Reading Component Manifest - Assembly
Info Reading Component Manifest - File
StartJob Starting Package Uninstall
Info Starting Package Uninstall - WROX_GuesbookVB
Info Starting Component Uninstall - Script
Info Begin Sql UnInstall
Info Executing Uninstall.SqlDataProvider
Info Start Sql execution: Uninstall.SqlDataProvider file
Failure Exception - Could not find file 'C:\inetpub\wwwroot\DotNetNuke\Uninstall.SqlDataPr ovider'.
Info End Sql UnInstall
Info Component uninstalled successfully - Script
Warning Component Uninstalled with Warnings - Script
Info Starting Component Uninstall - Module
Info Module un-registered successfully - WroxGuestbookVB
Info Component uninstalled successfully - Module
Info Component Uninstall Successful - Module
Info Starting Component Uninstall - Assembly
Info Assembly unregistered - bin\Wrox.Modules.GuestbookVB.dll
Info Component uninstalled successfully - Assembly
Info Component Uninstall Successful - Assembly
Info Starting Component Uninstall - File
Info Component uninstalled successfully - File
Info Component Uninstall Successful - File
Warning Uninstalled with Warnings - WROX_GuesbookVB
EndJob Uninstalled with Warnings

msellers · February 1st, 2010, 01:50 PM

Yes, you are going about it the correct way based on the changes to the DNN system. The no visible update is something that I hope will change soon.

As for the error, it looks like the file path isn't correct for the uninstall file.

shirk99 · February 1st, 2010, 02:36 PM

Thanks for the quick reply. I figured out the error. My <basePath></basePath> elements were all lowercase, and thus ignored.

Is there a concise resource available to the book owners that is kept up to date, listing all of the changes necessary to stay current with newer dnn versions and outlines error corrections?

msellers · February 1st, 2010, 02:39 PM

I am working on trying to get something in place.

This change with 5.2.x was not something I was expecting, I'm going to at least try to get things like this on my blog as quick as I can.

shirk99 · February 1st, 2010, 03:02 PM

When you have a chance, will you test this new 5.2.x "create new module" feature with your own .dnn file from the book exercises and let me know if it is working for you.

I installed the module, and ran the sql script. No errors. So far I'm up to page 148 and things are ok until I go to test the module.

On the Home page, the module appears in the module dropdown selection area of the control panel. I add it to the page and nothing appears. As a test, I added several HTML modules - this works fine. I tried typing in a title before adding the GuestbookVB module just to see if the title would appear on my page, but it doesn't.

Thanks for the assistance.

shirk99 · February 4th, 2010, 01:07 PM

My boss wants me to get this module creation figured out so I'm going over my work to see if I can pin point why I can't add my module to my homepage.

At this point, when I create the new module with the dnn manifest using the new process in 5.2.x, I still have the problem with the screen not showing any results or errors (see page 147, figure 9-3). But the new module is listed when I return to the modules area. The SQL script reports success when I run it. The homepage of my dnn site has the module listed in the dropdown box, along with all of the default modules. When I add it to my page, nothing happens. No module, no shell where the module is supposed to be. Other modules work properly. After going over my work and comparing the book / my project to a free module I downloaded, I have several questions and requests for clarification.

1. In VS 2008, go to the properties of the "My Project" file => click on the "compile" tab. Should the "Build output path:" be "..\..\bin" or "\bin"? By default it is "..\..\bin"

2. In the .dnn manifest file, go to the <component type="Assembly"> section. Skim down 4 lines. Should the <name> value be "Wrox.Modules.GuestbookVB.dll" or "WroxModulesGuestbookVB.dll"? The dll file in our project is named "WroxModulesGuestbookVB.dll" - different than the 'name' value in the book. Wasn't sure about this.

3. Found a typo on page 71 for what it's worth - Near the end of the .dnn manifest, in the <files> section, locate the file with the name of "Settings.aspx". This should be "Settings.ascx".

4. In the .dnn manifest, is the <supportsPartialRendering> value ('true' or 'false') case sensitive? In the book, you have it both ways. Page 143 has it lowercase, where earlier in the book it's uppercase.

5. In the .dnn manifest, in the <files> section, are the <path> values case sensitive? The values are all lowercase for "app_localresources" but the folder in our project is "App_LocalResources". Wasn't sure. Sometimes these things are picky about case.

6. On page 142, listing 8-19. Should the <moduleControl></moduleControl> elements be wrapped inside of a <moduleControls></moduleControls> parent element, as they are in listing 6-15?

7. This may be an oversite on my part that is common knowldege to most people - on page 144 it states that at this point we have a project that can be fully compiled. Should we be doing a 'Build' => 'Build GuestbookVB' from the VS menu to compile the module into a dll? Originally, I skipped this part until I wondered how the .dll file gets created.

8. Related to compiling the module, where should our .dll files be located if everything worked? In the project's own \bin folder, or the \bin folder for the DotNetNuke site.

9. This is related to the previous question. Keeping in mind that the default project setting is to put the .dll file in the DotNetNuke website's \bin folder ("..\..\bin") -- Do we need to manually create a \bin folder in our project root and copy the .dll file to it? I'm confused over this \bin business. Page 149 mentions the \bin being in the .zip file, but the bin folder is never created by VS when it creates our project folder structure, or by the reader via instructions in the book.

I skimmed ahead in the book and don't see anything to clarify the above questions.

Thanks!

waynb · February 9th, 2010, 04:19 AM

Hi, I need the Import module definition functionality. When will it be back?

I upgraded to DNN 05.02.01 (54)

Was it deliberatly deleted or is this a bug?

Thanks

Wayne