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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why should I NOT use DotNetNuke?Why should I NOT use DotNetNuke?
Previous
 
Next
New Post
8/31/2006 4:26 PM
 
Hi all,

I've looked around these forums and the internet over the past few days trying to get a handle on DotNetNuke, so I figured I'd turned to the experts.

Basically, I want to know if there are situations in which it doesn't make sense to use DotNetNuke? I'm not looking to bash DNN; it's obviously extremely powerful and extremely flexible.


For example,
1. If I want to reduce dependency on JavaScript
2. If I want to avoid overhead with markup and processing time since we don't have a need for skinning, etc
3. If we already have a fairly significant codebase written for a custom framework
4. If we want to get very specific with the markup that's being rendered
5. If we need a more featured CMS than the one provided with DNN
6. If we want the some of functionality provided in DNN (forums, blogs, etc) but with significant customizations

Also, we'd really like to avoid modifying the source code for the DotNetNuke framework if at all possible (to ease upgrade/staff turnover issues) so while I understand that most concerns can be resolved by "modifying the source," we'd rather not open that can of worms right now. Modifying source for modules is less of a concern.


Any other, maybe even higher-level situations in which DNN would not be a good fit?


 
New Post
9/2/2006 8:19 AM
 

Design=Choices.

 

You have provided some pretty vague issues so I think you’ll need to provide a little more specific information.

1)      Sure it can be removed, along with the functionality it provides.

2)      How do you not have a need for a page layout of some sorts?

3)      Depending on the original design it should be able to be ported or referenced from DotNetNuke.

4)      What can’t be rendered?

5)      What features?

6)      Ok.  

 

Since all projects are modules under DNN, you really don’t need to modify the core.  Any competent programmer can manage the framework in a relatively short period of time.  So far, your requirements do not specify why you could not use DotNetNuke in the first place.

 

It sounds to me like you would like a highly customized system with no page formatting, that has to be unaffected by advances in technology or upgrades, and it should work out of the box.

 

If your budget is between 6 and 7 figures, you might find a solution some day. Or you can have DotNetNuke up and running in a few hours for less then the cost of your morning coffee.


Dwayne J. Baldwin
 
New Post
9/2/2006 8:52 AM
 

DNN is growing exponentially and most of what you mentioned is already done or can be customized in DNN.  I agree with the last Reply, you have the option of spending the $$$ for software (not to mention more $$$ for support/ R&D) and who knows what else or utilize the power of this rapid growing community and its talented contributors.

To clarify your needs you may want to mention more details of the platform you are currently utilizing and what your goal is for this new project or system etc.  It seems too vague ...

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Why should I NOT use DotNetNuke?Why should I NOT use DotNetNuke?


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