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?