Last post Oct 04, 2005 07:43 AM by NDLanding
Sep 29, 2005 12:40 PM|NDLanding|LINK
Sep 29, 2005 03:11 PM|adefwebserver|LINK
Sep 29, 2005 03:44 PM|jjohns09|LINK
Sep 29, 2005 04:36 PM|GOHDS|LINK
If you are strictly writing dnn modules you should adhere to the dnn way of doing things. However if you are developing software applications there are other things to consider.
I'm the process of developing a big application over 50 table many many user controls and just didn't see a fit for the dnn way doing things so id decided to build my own framework
Here's my reasoning
1) I need to be the master domain, so i developed and interface between dnn and my application this way i don't need to worry about things that i have no control over. There's several modules out there that let you this or you can roll your own, it's not
2) I let dnn do what it does best manage the security and content of the website for my application.
3) I use the dnn code for reference, and learn and draw from it
4) Open Source is great, but when you are selling software applications to businesses, you better be in position to support your code, your clients are going to be looking at you for answers, not the core team not this forum.
5) What about if you want port your app to another portal, or another environment or make it a stand alone app. If your code has dnn dependencies you may end up with two or more versions of your app
Sep 30, 2005 05:54 AM|NDLanding|LINK
Sep 30, 2005 08:12 AM|timrolands|LINK
Sep 30, 2005 08:32 AM|GOHDS|LINK
Sep 30, 2005 01:29 PM|mzns1|LINK
Oct 04, 2005 07:39 AM|NDLanding|LINK
Oct 04, 2005 07:43 AM|NDLanding|LINK
Thanks for the pointer - I'll take a look also.