Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Bad module installation kills entire portal on dnn 4.9.4Bad module installation kills entire portal on dnn 4.9.4
Previous
 
Next
New Post
7/2/2009 12:59 PM
 

I did not see a forum for posting bugs, so this area seemed most appropriate.

This is quite frightening. I downloaded the starter kit for dnn 4.9.4. I created a new dnn portal module project from the template using vs 2008 express web (coded in c#). I was trying to follow the Album tutorial, but couldn't b/c it was using version 5 features. I decided to just install my blank module. I uploaded it to both my online and my local dnn site and it crashes the entire portal. You can't login or click on any links. It seems like only the home page loads initially. Everything else beyond that crashes the portal.

My zip included these files:

01.00.00.SqlDataProvider

Album.dll - I think this is what goofed things up. I renamed the generated dll to this. It was originally named YourCompany.Modules.Album.dll.

Album.dnn - will list contents at end of post

EditAlbum.ascx

EditAlbum.ascx.resx

Settings.ascx

Settings.ascx.resx

Uninstall.SqlDataProvider

ViewAlbum.ascx

ViewAlbum.ascx.resx

 

Here is my manifest:

<dotnetnuke version="3.0" type="Module">
  <folders>
    <folder>
      <name>Album</name>
      <friendlyname>Album</friendlyname>
      <foldername>Album</foldername>
      <modulename>Album</modulename>
      <description>A Album module</description>
      <version>01.00.00</version>
      <businesscontrollerclass>YourCompany.Modules.Album.AlbumController</businesscontrollerclass>
      <modules>
        <module>
          <friendlyname>Album</friendlyname>
          <cachetime>0</cachetime>
          <controls>
            <control>
              <src>DesktopModules/Album/ViewAlbum.ascx</src>
              <type>View</type>
              <helpurl></helpurl>
            </control>
            <control>
              <key>Edit</key>
              <title>Edit Content</title>
              <src>DesktopModules/Album/EditAlbum.ascx</src>
              <type>Edit</type>
              <helpurl></helpurl>
            </control>
            <control>
              <key>Settings</key>
              <title>Album Settings</title>
              <src>DesktopModules/Album/Settings.ascx</src>
              <type>Edit</type>
              <helpurl></helpurl>
            </control>
          </controls>
        </module>
      </modules>
      <files>
        <file>
         <name>Album.dll</name>
    </file>
        <file>
          <name>ViewAlbum.ascx</name>
        </file>
        <file>
          <name>EditAlbum.ascx</name>
        </file>
        <file>
          <name>Settings.ascx</name>
        </file>
        <file>
          <path>App_LocalResources</path>
          <name>ViewAlbum.ascx.resx</name>
        </file>
        <file>
          <path>App_LocalResources</path>
          <name>EditAlbum.ascx.resx</name>
        </file>
        <file>
          <path>App_LocalResources</path>
          <name>Settings.ascx.resx</name>
        </file>
        <file>
          <name>01.00.00.SqlDataProvider</name>
        </file>
        <file>
          <name>Uninstall.SqlDataProvider</name>
        </file>
      </files>
    </folder>
  </folders>
</dotnetnuke>

 

The module uploaded just fine. No errors. I did not verify the manifest, but I should be able to trust the installer when it says thing were successful.

Try this on your own (non-important, non-production) portal and watch it fail. I'm working on trying to fix it w/o a clean install as thats really no solution at all. I think I just have to update the dll file name to what it was and that may fix this.

 
New Post
7/2/2009 6:54 PM
 

thats an interesting problem you have there. Most probably it is caused by the business controller class reference

<businesscontrollerclass>YourCompany.Modules.Album.AlbumController</businesscontrollerclass>
 

Probably the best solution is to rename your dll back to YourCompany.Modules.Album.dll.

Here's why:

It is good .net practice to name your assembly the same as the base namespace you are using. In DNN it is also very important to make sure that your assembly has a unique name, so you should include something private in the name of the dll. For companies that is usually the company name, if you are a private person, you could use your initials or some other unique string.

The documentation of the help file includes some information about renaming the  "YourCompany" text in the template to something that is specific to your situation. You can do that quite easily by using the visual studio replace in files option. After that you only need to change a few things: the assembly name in the project properties, and any other file that includes yourcompany in the filename

also: you now learned an important lesson: alwas backup before you start to experiment with stuff....


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Bad module installation kills entire portal on dnn 4.9.4Bad module installation kills entire portal on dnn 4.9.4


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out