Thanks, I will have a look.

Sam

Dave,

This is a brilliant reply so thank you. I concur with your SP points although I was not aware of the development and performance issues with SP. Having said that I do find that SP requires a very sizeable infrastructure to run ie a fully fledged server farm with Search Services and form servers etc. I am just getting into it, but am finding the server admin stuff quite involved.

DNN always struck me as leaner and meaner !! However it does lack some of the more corporate aspects such as workflow and tight integration with office that SP has. I do however realise that DMX has some great WebDav functionality. Also David Washington seems to be doing some great work with WWF over web services with DNN.

Your comment about SP being a poor development environment did surpise me, but I am a novice with SP. I was of the impression that much of the extension work was about webpart development using ASCXs etc which effectively plugged in, perhaps I am in for a nasty shock.

In this tight economic climate I believe that companies are looking to tighten their processes hence the need for this type of system, but Business process automation requires good workflow. Also linked to this is the need for businesses to be compliant to whatever regulations are applicable to them and again this means "Auditable" workflow and an opportunity. It would be great to be able to offer a DNN based solution.

Lastly, and probably most importantly. I still believe that companies will plumb for SP because it is MS and they feel comfortable with it. Although far more expensive they feel it offers a better corporate fit. Therefore for folks like me it would be stupid to avoid SP since to me there seems be many companies who have bought their SP licences and want to find as many ways of extracting value from them.

Finally, Finally I believe that v5 DNN will be a really interesting release with its improved performance and XHTML compliance etc... So cannot wait.

Thanks,

Sam

P.s Module cost really interesting compared to SP, and an important point especially for solutions providers like myself.

 The large amount of code for DNN that exists "out there" to be reworked to deliver solutions is very important.

So far you have been able to bid a job where you wrote a large amount of the code yourself even if you were using DNN or SP. Trust me that will change (it is already changing). Campanies cannot pay you $15k to deliver a simple portal to exchange documents while they are laying off 40% of their workforce.

Many programmers do not remember 12 percent unemployment rates. When they return you will see those big fat corporate contracts dissapering. Meaning you wont have to argure with the "Architect Guy" because his job wont exist.

This is a huge reason to use DNN.