Dear visitor, thanks for stopping by! If you want, you can follow all updates on Snowball.be via RSS. You can also follow me on Twitter or Facebook. More interesting posts from other Microsoft Regional Directors can be found at The Region.
Gill Cleeren     DotNetNuke     January 6, 2007    

From DNN Creative magazine - very interesting if you're using DNN for large projects:
To help you consider which type of portal you should create, or whether you should create a new DotNetNuke installation, we have created a PDF mind map diagram which you can download for free.

Portal Considerations


We have based this diagram upon you currently having a single DotNetNuke installation with one domain name.

The main points that you need to consider are:

  • Do you wish to create several un-related websites with unique domain names?
  • Do you wish to create several websites of a related category to the first website?
  • How large and complex do you anticipate the website will become?
  • What are your hosting options, backup options etc?

The PDF diagram helps you work through each of these points and make a decision on whether or not to create a parent portal, child portal, or create a new separate installation of DotNetNuke.

Download the DotNetNuke Portal Considerations PDF diagram

  Posted on: Saturday, January 06, 2007 10:56:28 PM (Romance Standard Time, UTC+01:00)   |   Comments [0]
         
Gill Cleeren     DotNetNuke     January 4, 2007    

Today, while I was working on a DotNetNuke project, all of a sudden, I got the following error: System.Security.Cryptography.CryptographicException: Bad Data.

After some searching, I found out that this was caused because I was trying to work with 2 DNN portals at the same time.

If it still doesn't work after you close 1, clear your cookies.

  Posted on: Thursday, January 04, 2007 1:50:17 PM (Romance Standard Time, UTC+01:00)   |   Comments [0]
         
Gill Cleeren     .net | ASP.net | C# | DotNetNuke | Programming     January 1, 2007    

Lately, I have been doing a lot of projects with Dotnetnuke. I first started using it for my own use, but lately, I have used it to create some large portal sites for some of our customers.

To start with, let me first introduce Dotnetnuke (DNN). The very first sentence on the DNN homepage states the following: DotNetNuke is an Open Source Framework ideal for creating Enterprise Web Applications.

Let’s analyze this sentence, shall we? For starters, it’s a framework that you can use out-of-the-box to set up a portal site. Included in the download package are a number of modules that are sufficient to build an entire portal. Modules included vary from a simple HTML module to an entire forum and an image gallery. Of course, these are not enough to build an entire enterprise application. But DNN is very versatile, and so for every need, new modules can be build.
Since it’s an open-source project, it’s easy to tweak the framework where needed, to meet the needs of the application you are designing with it.

Sometimes, if an web-application is needed very fast, nothing comes close to use a portal framework like DNN. Lately, I have built the new Visug (Visual Studio User Group: www.visug.be ) site with DNN. We needed a site quickly, and DNN brought us the solution.
Some people I met are skeptical towards the use of DNN. The main concerns are mostly speed, reliability and not being in control. Personally, I admit that sometimes the latter can be true. I have had some problems with included features that are hard to override or undo. But since it’s open-source, I have been able to conquer them all.

One little thing, though. DNN is written in VB.net (the core and the core modules, that is). If you’re like me and you don’t program in VB.net, but still want to develop modules, you can do so in C#! Since Visual Studio 2005, it’s not a problem to have a solution with VB.net and C# files. Should you require to modify some core settings, you’ll have to write your code in VB.net, however.

So, now that I have been using DNN for several large projects, I have decided to share my knowledge on it via a series of articles.

In the first article, I will discuss how to install DNN and create the first portal with it. In the articles to come, I will show you how to create a module, how to skin the portal and how to extend DNN to use it to create full enterprise applications where DNN is used in a SOA environment. Stay tuned!

  Posted on: Monday, January 01, 2007 3:29:31 PM (Romance Standard Time, UTC+01:00)   |   Comments [2]
         
Gill Cleeren     DotNetNuke     September 6, 2006    

Today, while working on a DotNetNuke project, we had a weird problem: events, such as button clicks, selection changes... where not raised when we were logged in as a user with no edit rights for the role(s) he belongs too.

The problem appeared to be intermittent: sometimes it worked, sometimes it didn't.

After some testing, we found out that the problem is caused by the module being cached. Setting the cache duration to 0 solved the problem.

  Posted on: Wednesday, September 06, 2006 5:48:07 PM (Romance Daylight Time, UTC+02:00)   |   Comments [0]
         
9/2/2010   9:28:36 PM