Last post Oct 13, 2005 07:36 PM by GOHDS
Oct 04, 2005 07:06 PM|swonderme|LINK
Oct 04, 2005 10:49 PM|nbc|LINK
Oct 05, 2005 08:56 AM|dnncreative|LINK
Oct 05, 2005 09:57 AM|GOHDS|LINK
I'm currently writing a major applicaton for vertical market, just like you are planning to do and like you i'm a one man show.
Some things to consider and plan
1) Define clear roles for dnn and your application. In my view the app should be the master of its domain. I let dnn manage the security and the page content.
2) Do you plan for your applicaton to only to run in dnn? If you want your app to be portable, then your need to layout your projects so they have no dnn dependencies. I architected my app so it can run easily run in other environments
3) Is your app going to be sold as turnkey solution? Then you need to have a good installation package. You also need to settle/lock in on a version of dnn.
4) Where is your app going to run. Is a hosted solution, or an intranent, or business to business, each one of this has own issues.
5) If you are going to offer your app as hosted solution, how you are going to charge per use, flat fee or per seat?
6) Do you plan to sell this to differnt businesses. If so then think of how you are going deploy new releases, coordinating database changes to your user databases. I use SQL-Compare from red gate for my managing my database changes
7) Does your application have roles? Plan on how your going to integrate dnn role based security with your app
8) What language is your app going written? Writing your app in vb allows you take advantage of the dnn codebase.
9) Settle on a good DataAcess Layer generator and make sure you can work with the code it generates. It should allow you build and rebuild your data tier with a one click operation and it should not interfere with your hand crafted code . I ended up writing
My advice to you is to begin with the end mind. Achitecture before code.
Oct 05, 2005 02:53 PM|swonderme|LINK
Oct 11, 2005 09:40 PM|RobertKGaudet|LINK
Oct 11, 2005 11:48 PM|GOHDS|LINK
My dal is something, i have grown over the years, before i got involved with dnn. I need it something that worked both in widows or web developement. That's was t-sql oriented. Being a one man shop i'm the architect, the dba, the developer. I do most my
heavy lifting in store procedures. My DAL accommodates datasets, datatables and dataviews, that would allow me to easy manage connection strings.
I use an earlier version of Microsoft daab, ( i think it was called dbhelper then ). I can point the program to a applicaition database and a project folder it creates the CRUD store procedures and wrappers for all the application tables. It also creates
wrappers for the non-cruds store procedure and my views.
Whenever i make changes to the database add new fields, new sprocs or views, i can just run the program with one click, it picks up all the latest db changes and updates and it recreates all the code on a separate project.
The DAL generator is written in vb and it uses sqldmo to derived the database definitions. If you are interested in the code shoot me an email
Oct 13, 2005 09:58 AM|RobertKGaudet|LINK
Oct 13, 2005 07:36 PM|GOHDS|LINK