When you drag the 3rd part control onto a user control, it automatically adds the entry into the web.config.

It is caching but not the module caching within module definitions in the host menu.

It is the cache setting under "Page Settings" within an instance of the module (modules settings) (if that makes sense ).

If I set it to 60, the events stop working. If I set it back to 0 the events are triggering normally.

Hi folks,

First off - thank you very much for posting and answering this question. This was exactly the issue I was having on a custom module that I was creating...and this has been driving me absolutely NUTS for the past couple days.

In my case, I had a module with a ASP.NET Calendar control - and the events were not firing for unauthenticated users for changing the calendar month (clicking the '<' and '>' links) nor for any 'view details' links I placed in the day boxes.

Setting the cache to 0 on the module definition and the page's cache setting worked like a champ. I would like to be able to take advantage of caching for this (as the rendering of multiple calendar listings down to a page can potentially be intensive), but it's more important that it works. :)

Again - thank you guys sooooo much. You would not believe how much grief this has caused me over the past weekend. I thought at first it was the starter project (I've had several odd behaviors using the Starter Kit over the 3.x development methods) and thought this might have been another one -- and spent the weekend learning how to create a standalone project, and the whole 'Convert to Web Application' feature that I wished was better documented. ;)

BTW - Have I expressed my thanks? :)