browse by category or date

Semantically Correct

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant:

a picture is more than a thousand words

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant:

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 🙂

About Hardono

Howdy! I'm Hardono. I am working as a Software Developer. I am working mostly in Windows, dealing with .NET, conversing in C#. But I know a bit of Linux, mainly because I need to keep this blog operational. I've been working in Logistics/Transport industry for more than 11 years.

Possibly relevant: