The latest version of the Events module is in Beta...this is the last version for DNN 3 (furture versions will be DNN 4 and .NET 2.0).

We are looking at a re-write for the next version.  I will add a better Business Layer API that can be more easily used by other apps, including enumerators for property values...this is probably the biggest issue as I see it.  For example if another module wants to create a recurring event, currently they do not know how to set field/property values correctly w/o researching the bits.

Before I chime in about items the Events module may be lacking, I want to say that I like the module and am glad Alan joined the core team and opened up his AVCalendar code as the new Events module (thanks Alan!).

The Events module provides a great base of functionality.  Unfortunately, our needs vary by customer and we've had to make additions and modifications to satisfy everyone.  A few of the more notable examples of changes we've implemented:

• Modify order of elements on the event details page as well as font size and color (simple changes to .aspx page - no big deal)
• Provide users a way to "subscribe" to new event notifications (auto-email when a new event is created)
• Provide users a way to "one-step-subscribe" to event notifications for multiple event calendars (users can pick which calendars)
• Provide users a way to "one-step" create a new DNN user account and register for an event (this is a biggie for us)
• Provide admins a way to see rollup of multiple events including registration status, capacity and number of currently enrolled

In some cases we were able to write solutions that simply tapped the appropriate Event DB tables without need to modify any core code.  Some cases, though, required code modification.  We're now using a modified version of AVCalendar, a "forked" copy of Events and the default "Events" for various customers.  It'd be great to have a mechanism for extending "Events" without touching the core code since Events already provides 90% of what we need.