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...3rd party module paranoia3rd party module paranoia
Previous
 
Next
New Post
7/22/2009 10:58 AM
 

I try to stick to core modules as much as possible, and try to avoid 3rd party modules because in my opinion they are at higher risk of arrested development.

i.e. I don't want my site to rely heavily on a 3rd party module, upgrade to DNN5.1 (or 6 later) and then have it simply not work....

How often do 3rd party modules get broken by upgrading the core? What causes them to break? Shouldn't they run somewhat independently from different tables in the database?

All the third party modules I've purchased have a long history of good support, reviews, patches, multiple previous versions.... transition from ASP.NET 1.1 to 2 to 3.5, etc.

Does anyone know if, as ASP.NET continues to mature, Microsoft plans on always keeping it backwards compatible?  (I believe transition from 1.1 to 2 was a disaster, but I may just know what I'm doing!)

I'd like to start implementing some less established modules in my site, but I don't want to rely on them... any reassurance? 

 
New Post
7/22/2009 11:10 AM
 

m wrote


How often do 3rd party modules get broken by upgrading the core?

Frequently.  Pay attention to the module's developer for info.

m wrote

What causes them to break?

Lots of things.  Poor programming, changes to core APIs, unforseen possibilities, they aren't relevant anymore, etc.

m wrote

Shouldn't they run somewhat independently from different tables in the database?

How?  Do you want a third party module that doesn't understand the DNN membership system?  Loads an entirely new client framework API?  Modules will almost always have at least some links to existing DNN functions, that's the whole point of having a development fr4amework.

Jeff

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...3rd party module paranoia3rd party module paranoia


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