DNN is not a RAD tool or environment.  It's a framework, just as ASP.NET is.  For your project, you could use DNN, but think about why.  Are you needing a portal, with authentication, roles, community tools such as blogs and forums?  Or do you need a database that can be searched through a web interface?  Does it help to develop within the DNN structure, learning to produce modules that inherit and behave according to a specific development framework?  Or do you just want your web interface to be "catchy" with lots of web 2.0 whiz-bang features?  Do you have a team who will be working within the DNN framework for design and layout, coding and content development or publishing?  Or is it just you?  Will your replacement be able to maintain your application?

You're right to look at options.  Just be sure you evaluate them based on the project that needs completing.

Jeff

Geoff,

A big thank you for this.... Perhaps my definition of RAD is quite loose ie I am wondering whether it can be used as a tool to significantly speed up solution development.... I think it can due to its "Assembly" approach of modules and leverage of framework services.

I am a freelancer seeking a platform that will enable me to put solutions together much more quickly. Also it would be very helpful to have large 3rd party support for the platform in terms of knowledge and prebuilt components. Certainly DNN scores well with this ..... I have seen some very interesting 3rd party modules. However I want a big wide open door into ASP.NET2 so if I want to create modules easily using standard ASP.NET techniques then I can do so.... Also I have to admit that that my knowledge of ASP.NET2 is not as good as I would wish it and development is taking too long with pure ASP.NET2/C#. I see DNN as great short term way forward if not  long term due to its features... Yes I will be building some traditional DB apps so the question is would I be better off going with pure ASP.NET or with DNN with just the DB modules as needed but using all the great user/menu/skin servies etc....

There is always a temptation to cut your own code.... and I am challenging this... Assembly has always seemed more attractive to me..... with more time taken to seek out the best components rather than code .... and if really necessary building a components..... like building a car...

....but and this is an important "but" it can not be at the expense of performance....

Any Comments greatly appreciated...

Thanks in advance,

Sam