Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Development with DNN4, C# & VS2005Module Development with DNN4, C# & VS2005
Previous
 
Next
New Post
5/25/2006 2:03 PM
 

I am looking to develop a web-based application, using DNN4, C# and VS2005.  I have the following questions;

1. What is the best way to set up a development environment?  I've seen a number of posts/articles talking about this topic, most of which are dated, i.e. referencing DNN2 and VS2003.  I expect that I will be able to setup a new project, and simply make references to the DNN Core, but would be interested in hearing how someone else might have done it first.

2. For database connectivity, is it a better practice to set up a separate database?  My database will have enough tables that I think the "User Table" approach would not be feasible.  I expect that the database will host multiple customers, one for each portal, so it's tempting to just leave it in the DNN database and use the portal id as a key.  But, there are other reasons (performance, security, upgrade path, etc.) to separate, and I am looking for feedback.

If there are any articles/books/etc that are available, any mention of those is appreciated.

Thanks,

Chuck

 
New Post
6/7/2006 2:39 PM
 
Your development options are endless. Well, maybe not, but you can do it almost any way you'd like. You can create class library, web application, or web site projects. A number of people simply build their modules within the DNN project. Personally, I prefer the class library approach. You should try each to get a good idea of what works best for you.

As with every solution, there are pros and cons to everything. The biggest problem that you'll find is that if you opt to keep your database separate, you won't be able to take advantage of the database install/update scripts that are executed when you update your module. You can do this with extra code or have the user do it, either way, it's a lot harder than including it with your scripts. If your reasoning against having it in the same DB are greater than the time/money it'll take to do it separately, go for it.

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com
 
New Post
6/8/2006 1:03 PM
 

Michael,

Thanks for the reply.  I thought the post had gone cold!

I believe that any benefit about a separate db is outweighed by the install/update capability you mention.  Thanks for the advice.

Chuck

 
New Post
6/10/2006 3:26 AM
 

you can check out my module development approach - it should help you, and it is immune to the progamming language of the module (you can build your module as a C# project)

 


Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Module Development with DNN4, C# & VS2005Module Development with DNN4, C# & VS2005


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out