|Absolute Value|

I have been having some annoying permission problems with my subversion server. User X would update changes and then user Y would be denied access to the database. Worked out that even though all subversion users were part of the same group and the subversion repository was chowned to the subversion group, if the database created any log files, the log files would be created so that only the user who updated the repository will have write access.

After some searching on Google, this chapter in the subversion manual came up. All I had to do was create a wrapper for the subversion commands and make sure that a sane umask was set before the commands were run and everything is working perfectly. If you are considering running subversion over SSH, make sure that you comply with everything in the checklist.

In case you don’t know, subversion is a great source code management system. It is a lot more powerful than CVS and works really well with large binary files. Couple it with the windows subversion client, TortoiseSVN and its the easiest way to manage your source code.

However Visual Studio 2003 won’t open web applications managed by subversion because of a bug relating to the directory subversion creates called .svn. Visual Studio 2005 has this bug fixed so hopefully it won’t be an issue for much longer.

I arrived back from my little time off in South Africa. Slept the whole way back from SA and only woke up over Paris, so I feel great! This must be the first time ever.

I find this story today very ironic. Eminem recently cancelled a large quantity of tour dates as he said he is suffering from exhaustion. However, today the BBC reports that he is being admitted to rehab for addiction to sleeping tables.

Hmmm, I’ll let you guys work that one out.

I will be away for the coming week and back on Monday 29th August. I will be in South Africa for a week visiting my family and girlfriend who has been there for a month now studying. I can’t wait although the flights as usual are awful.

Any posts I do will be posted on Non-Tech-City so come on over and have a read!

From the comments in my previous post, I noticed that I hadn’t done my research properly around GPL licensing. Firefishy rightfully pointed out that the GPL doesn’t force you to contribute your code back, just that it forces you to provide full source code if you decide to distribute your modules and any other modifications you have have done.

Thanks Firefishy!

One of the great aspects of DotNetNuke is it’s licensing. Its license is based on the BSD license.

What this means is that the software is free for you to do anything you wish without having to submit any modifications or enhancements. This is really useful compared to the GPL where you would have to submit any changes as you will be developing custom modules for yourself that you would probably not want to share.

From their site:

*** Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise, arising from, out of or in connection with the software or the use or other dealings in the software. ***


We are currently using DotNetNuke as the portal platform for an in-house project. I chose this platform as our base because it is written in a .NET language (our languagues of choice), its add-on model is stable and incredibly sound and it has the ability to do pretty much whatever you require.

Looking the the object model within DNN, you will notice n-tier development at its absolute best. The 3 layers (data, business, presentation) are tightly defined and completely seperate. The platform does run off a SQL Server backend but because of the architecture, I could easily write a MySQL dataprovider or an Access version if I really wanted to. As an example, in the business layer all datareaders are passed around as an interface called IDataReader. The business layer doesn’t care what kind of datareader it is (ODBC, SQL) as long as it implements the functions defined in the IDataReader interface. Pretty smooth!

If you are wanting to learn how a well architectured application works and how n-tier applications are built, take a look at the source code, install the portal and have a go at writing a simple addon. You won’t be disappointed and you will definitely learn something new about OO in your work.

It has taught me a lot and I am not even coding with it directly. There is a C# version that has been ported from the VB.NET version in case you prefer that language.

I have decided to write about our experiences using the portal on this blog. If you have an interest in DotNetNuke, n-tier development or just OO, subscribe to the RSS feed and have a read!

DotNetNuke Sourceforge Page
C# Version