I've been searching around the Wiki and the forums, and I haven't found very much on how to make a module with client script work with Module Output Caching. Here's the situation:

We are developing modules that require some client script to run. Normally we would just call ClientScript.RegisterClientScriptBlock or similar. However, this won't work if you enable Module Output Caching for the module. The module's final HTML output is saved to cache and subsequent requests just re-render that HTML. No module code is executed, so the RegisterClientScriptBlock is never called.

One option is to just the script in <script> tags within the module, so that the script is cached with all the other HTML. However, this can get tricky when more than one instance of the module is on the page. If that is my only option, I can probably make it work. But I'm curious if there is anything else I'm missing that would do a better job.

If anyone has tried this and has suggestions, please let me know.

-Drew

---

Andrew M. Galbraith Ryer

There is nothing like looking, if you want to find something. You certainly usually find something, if you look, but it is not always quite the something you were after.
     -J.R.R. Tolkein