ramsey:
Personally, I say don't bother with the DNP ecommerce; most of us are probably using third party solutions. I’d like to see better documentation for the API with asp, asp.net sample code. If one of our resellers wants a solution the basics are in DNPe. DNP should focus on being a great control panel not a control panel with an ok billing system.
I disagree. I'm using WHMCS myself as well but is very annoyed over having serveral systems from different manufacturers to work together even if they would work very good. I want to have it simple for my customers, one and only integrated all-in-one system, that being DNP.
Actually, as a developer myself I can't see the problem for DNP Team to either finish the eCommerce module and get it working as most customers would like to, or even with a total rewrite of a billing system it shouldn't take that long time. It's a disgrace, in my opinion.
Personally I'm convinced that DNP Team is more interested in developing modules like Hyper-V, Exchange and so on that they can earn much more money on, than taking care of us; the existing basic product customers. During the 1,5 year I've been a customer myself - what have i got with the product since then? A couple of bug fixes, a couple of provider version upgrades, a couple of headaches, and a non-working web application gallery. Oh - and of course a couple of cosmetic refreshes as well. The development is way to slow progressing for a promising and so far pretty good product.
But one of the worst things DNP Team can do to us is to be quiet, not telling us any road maps at all, not answering anyone in the support forums, and not publishing some real and working new features in the basic product. Sure the extra modules charged seperately is indeed nifty but way to expensive in my opinion, and interesting for the market in general but not for many of us "basic web hosting" customers to DNP.