While DNN Corp bears some responsibility for the stability of the platform, this is still an Open Source project.  Community members are encouraged to participate and help resolve issues when they find them, or when they have a fix.  We have not always done a good job of highlighting how people can contribute, but that is changing and I look forward to getting more and more community contributions in 5.4.3 and future releases.

As for the Telerik.Web.UI.dll in the upgrade packages - it is not missing and it is not a mistake.  It just doesn't exist in the bin folder as that would result in an error due to the AssemblyBinding entries in web.config.  When we upgraded Telerik in 5.4 we added a separate Telerik library (/install/module/Telerik_05.04.00_Install.zip) in the install folders so that the upgrade would make the needed changes to the web.config prior to putting the upgraded Telerik file in the /bin folder.

We perform a significant amount of testing on each release and for the past year that testing effort has been growing with each release.  We now have library of several hundred test cases that includes build verification tests, regression tests, and specific acceptance tests for new features.  We continue to move forward on automating as many of these tests as possible and adding in more and more unit testing.

We understand that the DotNetNuke Professional pricing may not be appropriate for some members of the community, even while a large number of companies find it to be a good value.  We are currently looking at ways to serve those members of the community who would like a lower cost option and are always interested in your feedback.

---

Joe Brinkman
DNN Corp.

Dave,
first off I'd suggest that you log your issue at support.dotnetnuke.com. Please log as much information as possible, ideally a step by step guide to reproduce. The QA team will then try to verify the issue, and if verified it then becomes possible for it to be worked on by the dev team/core team - if an issues not logged it unlikely to be fixed. Users can also vote on issues and therefore flag them as likely affecting multiple users - also a logged issue will frequently then be referenced in forum posts. We spend a lot of time in the forums and support and notice common/popular issues bubbling up, which leads to them leaping higher up the priority queue.

If you're looking for help via known experts the the dotnetnuke partner directory may be of interest - http://www.dotnetnuke.com/Partners/Pa... .
Alterntatively asking the community may be an idea (as some people will do things such as this in their spare time, it may be cheaper than engaging a company). Theres no forum on dotnetnuke.com that specialises in putting site owners in front of dev's, most people simply post a forum post with a relevant title e.g. "who can help me with a logon/register problem -will pay $" . Alternatively some sites such as http://www.dnnguru.com/ provide a service in putting people in touch with each other, or else non dotnetnuke specific sites such as http://www.rentacoder.com/RentACoder/... are popular.

Finally I'd always recommend you check the changelog before engaging in a task such as this - http://support.dotnetnuke.com/project... -you didn't describe your login/register problem, but a quick scan shows a few items in that area that have been resolved in the past few releases. I'd recommend you also test an upgrade to the latest version before seeking help.

Cathal

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US