We're currently beyond milestone 2 and working towards milestone 3 which is the milestone on which we'll release it.
Milestone 2 was the milestone where we would have ported everything over to .NET 2.0, llblgen pro v2.0 and have implemented all missing forms in the administration section, as well as ported all the hungarian coding over to normal coding style. (this forum was written in 2002 with the old llblgen 1.21 dal generator and is ported to llblgen pro bits by bits during the years but still relied on views and procs for 30% or so.)
In milestone 3 we'll just add new features. Below is the list of new features for M3:
* CSS usage is now too messy, it should be cleaned up. Usage of ASP.NET 2.0 skins?
* Add a user preferences section
* Help page is out of date.
* ThreadListInterval default should be defined in the forum entity DONE
* User last visit tracking should be done in the profile. DONE
* Add Custom Error page
* Show list of last 50 (or so) threads in which user has posted in the profile DONE
* 'New messages' marking should be done more cleverly DONE
* Add 'private thread' feature
* Sections and Forums should have an order in which they're listed
* Threads should get a # of views counter DONE
* Ability to attach a file to a posting and/or thread
* Ability to email a user when a new post is made in a thread
* Active threads should be managed through queues. DONE
What we want to achieve is that the forum software gets a private section in which registered users can start threads which are visible to only support team members, admins and the thread starter. This then allows us to drop the helpdesk system we're currently using which has proven to be not that useful to us. The main gripe is that there are two queues to look for questions to answer. With the new support queue system implemented, it's very easy and support team members can move threads to different queues, claim threads etc.
There's still work to be done but I'm confident it's done by the end of october. It will be released with full sourcecode and a friendly OSS license (have to select which one) as an example how to use a part of the LLBLGen Pro featureset in a real world application.
We're still looking for a name for it though. If any of you has a suggestion, let us know