We are currently developing a CMS project in ASP.NET, utilizing jQuery for our client-side scripting needs.
At the moment, our project includes the jquery-1.2.6.js file as a mandatory script file. Additional script files are loaded as needed, based on the components being used by the CMS editor on a particular page or template.
Many script combiners generate a static script, which would require us to include all possible script files in advance to ensure they are available when needed. Since we are not incorporating any ASP.NET Ajax extensions, we have not explored the benefits they may offer.
Any suggestions for our situation?
Although I have reviewed Combining and Caching multiple JavaScript files in ASP.net, it does not address the specific nature of our conditional requirements.
Fortunately, I have discovered that using ScriptManagerProxies and certain methods on the base master Page can be a solution. However, another issue arises: preventing unnecessary ASP.NET Ajax content from being transmitted to the client. I plan to implement bleroy's hack until the release of ASP.NET 4.0.
Thanks in advance.
Pat Long