Hi All,

I am wanting to build a supplier directory type web application which would normally require a straight forward ASP.NET/DB approach. However I am wondering whether to use DNN as a platform since it has so many features. I guess I would then be looking for DB search modules etc. What is your view on this? Should DNN be left to colloborative and general portal type apps such as news, links, blogs etc rather than a specific DB styled web app. Also if I did do my own ASP.NET2 app it would be in C#.

One thing that does concern me is the potential speed problem. I had some collegues who tried it as a virtual working tool, but gave up due to poor performance. They have used V3.... it was about 18 months ago. Interestingly I find this forum pretty slow... Whether this is DNN or poor connectivity or what I am unsure....

I would be hugely grateful for any advice.

Thanks in advance,

Sam

Shawn,

Many thanks for this. Some comments.

1) The main potential for DNN in my situation is to enable me to build an asp.net app very quickly with robust plumbing and features - An app in a few days rather than months. Also I am still learning ASP.NET and this is slowing me downing. Hopefully with DNN I can focus on the client, be "Agile" and deliver something of enterprise strength.  However I am a little nervous about being locked out from what I could do with standard ASP.NET? I assume the 2 worlds meet by the creation of modules.... which would be webparts in ASP.NET2.

2)I have researched the DB retrieval issue and seem to have concluded that I need to invest in a 3rd party module like "Indoo SQL Grid" or "XMod".

3) How easy is it to integrate ASP.NET2 controls such as a Treeview.... ie I have a need to use a Treeview to represents categories and would use it to drive searches rather than the standard keyword approach. In ASP.NET2 I would just link a few controls together using code...

4) I am using the latest version and finding the speed OK, but when starting up it can be slow.... compiling up no doubt. Can you precompile the code to prevent this initial hit like you may do with a standard ASP.NET app?

5) Since DNN is a general container for applets(modules), Is there any issue with having a sperate database under a specific module. So one may use the standard DNN DB for security etc..... but have a completely seperate one for a specific application ie a supplier directory.

I really appreciate your help... and a big thank you in advance for help with this issue.

Sam

Leopold,

Many thanks for the prompt reply.

So in short do you see DNN as  a RAD application environment where solutions can be quickly and robustly assembled? I quess extra functionality would then be acquired by 3rd party modules or produced by writing a custom module.

On modules,

1) Is it simple to create custom modules ie as simple as creating ASCXs?

2) Can ASP.NET controls be involved easily into a DNN app? How could one create a Webpart or ASCX in ASP.NET and integrate it for use in DNN?

On a final note I notice that the speed can be very slow on this forum.... Sometimes OK , but then sometimes I have to wait 30 seconds for the page to change so I can put in a reply. Since you are a core team member, I thought you may be interested.

Thanks again, really appreciated,

Sam