SODEVE

Just solved a simple problem but took me hours to figure out the solution. So I will just share it here hopefully it will help you avoid the same mistake.

 

I have few DotNetNuke modules to be improved/debugged. So I managed to install the first module and improved it. When I tried to install the second module, DotNetNuke prompted me this:

So my immediate response was re-edit the manifest (.dnn) file. After validated it using DotNetNuke’s Manifest Validator (apparently it’s only an XML validator ^^!), I reinstall the module. Still the same error.

 

Strangely when I check the Module Definition Page, the module is actually installed. The DNN Manifest declared 4 Module Definition, but apparently only 3 added. When I tried to add the fourth Module Definition manually, it prompted me, “Module Definition is already exist”. EUREKA!!! (unlike Archimedes, I was not in the bathtub and then running around the village naked. I just running around in my house, fully clothed, of course :-))

 

So I compared the both DNN Manifest files. Snippets from the first DNN Manifest:

    Statistics
    
        
            DesktopModules/FirstModuleName/FirstModuleControlName.ascx
            View
        
    

 

Snippet from the second DNN Manifest:

    Statistics
    
        
            DesktopModules/SecondModuleName/SecondModuleControlName.ascx
            View
        
    

 

CONCLUSION: DotNetNuke’s Module Definition Friendly Name Is Unique

Hardono Arifanto :: Apr.21.2007 :: Programming, .NET :: No Comments »

When adding a DotNetNuke module to a DotNetNuke page, you might experience errors. The following checklist hopefully will able to help you to correct the errors:

1. Check your Module Definitions. Make sure in every module definition you only have one Default control. Except the default control, the Key for any control must not blank and have a unique name
2. Make sure you compile the module project with a proper Assembly Name and correct Namespace
3. Make sure you have run the SQL Script (if you install the module without using DotNetNuke Manifest)

These errors have made me wasted hours of coding. Hopefully it helps everyone in one way or another.

 

If you have other problems and not listed here, let’s discuss it here

Hardono Arifanto :: Apr.15.2007 :: Programming, .NET :: No Comments »

Apparently installing DotNetNuke is quite tricky. I did make a few mistakes which wasted a few minutes. So hopefully this post will save you from hassle.

1. Get your Internet Information Server (IIS) up and running

   IIS is by default available on Windows 2000 all version, Windows XP Professional, Windows Server 2003. If you have Windows XP Home Edition, don’t worry. This hack should help to get IIS installed on Windows XP Home Edition. To confirm your installation click this HERE.

2. Install .NET Framework 2.0

   Get your .NET Framework 2.0 HERE. The trick is always to get .NET Framework installed after your IIS confirmed up and running. You can’t do it the other way round. For most Windows XP installation, usually .NET Framework is already installed by default. If you happen to have such condition, you need to uninstall your .NET Framework, confirm that your IIS is up and running and then you proceed to install .NET Framework.

3. Download DotNetNuke

   Although I recommended .NET Framework 2.0 at step 2, DotNetNuke older version is running on .NET Framework 1.1. So if you haven’t upgrade your .NET Framework to 2.0 and you don’t have intention to do so, download the DotNetNuke version 3.x. Otherwise, download version 4.x. The download page is HERE.

4. Setup the Folder

   Extract the archive you download in Step 3. In this example we will assume the installation folder is C:\DotNetNuke. Right-click on C:\DotNetNuke folder, click Properties. On the General tab, make sure the Read-Only checkbox is not ticked. On the Security tab, add user “ASPNET” and give it Full Control access rights. You might want to add user “IUSER_YOURCOMPUTERNAME” (the IIS guest account) and give it non-Write access rights.

5. Setup the Virtual Directory

   
   Open the IIS Management Console. You could do it by Start-Run-type “C:\Windows\System32\inetserv\iis.msc“-OK, or by Start-Run-type “compmgmt.msc“-OK continued by browsing to the IIS section. Right-click on the Default Web Site, New -> Virtual Directory. A wizard window will show up, click Next. Put DotNetNuke in the Alias text box, click Next. Browse to “C:\DotNetNuke”, click Next. Tick Read and Run Scripts only, click Next. Click Finish.

6. Install Database

   Although DotNetNuke supports not only MS SQL Database, I have yet to research them. In this opportunity, I will only discuss about MS SQL. Hopefully someday I will have time to test DotNetNuke installation with other type of Databases and report it there. Okay, first you need to download your copy of MS SQL Express Edition. You can downloaded it HERE.

7. Setup Database

   
   Open your SQL Server Management Studio (Start -> All Programs -> Microsof SQL Server 2005 -> SQL Server Management Studio). Click Connect. Above Database, Right-click -> New Database. Give the database a name, in this case we will name it MyDNN and click OK.

   
   Go to Security -> Logins. Above Logins, Right-click -> New Login. Type the Login Name –we will call it myDNNuser and then change the radio-button into SQL Server Authentication, and then type the password and confirm it, and then select the Default Database (i.e. MyDNN), and finally click OK.

   
   Go back to the MyDNN Database -> Security -> MyDNNuser -> Right-click -> Properties. Make sure db_owner on the “Schemas owned by this user is ticked”

8. Edit Configuration File

   On the folder “C:\DotNetNuke” you will find web.config, edit it. If you could not find web.config, rename release.config into web.config. Look for a tag called <connectionStrings>. Inside it, comment the first child tag and uncomment the second one. Make sure you put the correct value in that tag. (i.e. value=”Server=YOUR_ComputerName\SQLEXPRESS; Database=myDNN; uid=myDNNuser; pwd=the_password;”). Do the same on the other tag called <appSettings>

After this you need to point your browser to “http://localhost/DotNetNuke/Install/install.aspx”. The installation should be automatic. Problems? Critics? Suggestions? Just drop your opinion on the comments.

Hardono Arifanto :: Mar.31.2007 :: .NET :: 2 Comments »