I believe I found the problem..I have EpiFrame on my portal, and in order for it to work this has to be commented out in the web.config:

<buildProviders>
        <!-- <remove extension=".resx"/> -->
        <!-- <remove extension=".resources"/> -->
      </buildProviders>

When I uncommented those 2 lines in the web.config, the events module worked but now epiframe did not.  How come your previous beta versions of the Events module worked just fine with those 2 lines commented?  Is there any way the events module can work with those 2 lines commented?  Thanks again!

----------
Hey favance, just downloaded the lastest version 03.03.05 and am getting an error message when the module displays.  I uninstalled the previous Beta version 03.03.02 and did a fresh installation of 03.03.05..everything installs properly without any errors.  Any idea what may be causing this problem?  Thanks so much for this module and your help!

Error: Events is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Cannot find a name for the resource with the value ''. Line 508, position 10. ---> System.Web.HttpParseException: Cannot find a name for the resource with the value ''. Line 508, position 10. at System.Web.Compilation.AssemblyBuilder.AddBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) at System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) at System.Web.Compilation.BuildManager.EnsureFirstTimeDirectoryInit(VirtualPath virtualDir) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace ---

Sorry about the "All day" event...I really would like to hear some ideas about the "Use Case"...if it's as simple as just a check box for "All Day" and default the begin/end date time to the selected date, then this should not be that difficult.

Not sure what your're looking for in the hover tooltip...again a use case would be helpful.

As far as the release, I'm working through the process as we speak.  The new process for DNN Modules is designed to improve the reliability and support for DNN Modules as has a few requirements.