On page 142 & 143, the tags that appear in listing 8-19 and 8-20 are slightly different than what is in the actual project file. For example, the book says that the new module definition starts with a <moduleDefinition> tag. The actual source file in the project contains a tag named <module>. Other examples are <moduleControl> vs. <control> and <controlType> vs. <type>.

I am building the sample project in VS 2008 with a DNN 5.0.1 installation. Maybe the difference is due to something that changed between DNN 4 and DNN 5.

Jim

Also, listing 8-20 (VB Manifest Module Addition) adds:

<controlSrc>DesktopModules/GuestbookCS/Settings.ascx</controlSrc>

Go back to Listing 6-15. If you follow the instructions there and "entirely replace the text of the .dnn files generated by the templates," the issues with the tags will be cleared up.

Don't worry. I made the same mistake. There were a lot of code examples up to that point in chapter 6 that were meant only to be read, not copied into the project. Perhaps the authors should have told us more explicitly to stop reading and start typing. It is ironic that the first thing we are supposed to type into our sample project is the entire .dnn manifest, the most unfamiliar component of the whole process. No wonder we didn't do it.

Also, the instructions at 6-15 say to replace all occurrences of GuestbookCS with GuestbookVB to create the VB.NET manifest file. So, my previous post is also handled by following the instructions more thoroughly.

- Paul

Paul and others,

Sorry about that, in reviewing the book, there are a few inconsistencies between the book figures/text and the proper ones.

Paul's approach outlined in the previous post is a proper workaround for the issue.

__________________
Mitchel Sellers
Microsoft C# MVP, MCITP
Director of Development
IowaComputerGurus Inc.

My blog for .NET and DotNetNuke info

Author of "Professional DotNetNuke Module Programming"

Author on "Visual Studio 2010 six-in-one" and "Pro C# 4.0"