Hello,

I am developing a module that will never be able to cache content, as it creates itself based on encrypted querystrings that are never used twice.  What is the best way to disable caching for this module at designtime so that implementers do not have to make this configuration change when deploying the module?

Thanks

Matt

I haven't had time to look into this anymore, but I did notice that there is a default cache value in the module definitions table...  so it might be something that can be implemented in the initial SQL script.  Let me know if you check it out.