The inclusion of WebResource.axd will be added by the controls (who needs it). They will not be added by IIS or the underlying ASP.NET framework.
So, for example, if the control has a dependency on the built-in webresource, it will do something like this:
string scriptUrl = Page.ClientScript.GetWebResourceUrl(this.GetType(), "RESOURCE_NAME.js") Page.ClientScript.RegisterClientScriptInclude("RESOURCE_NAME.js", scriptUrl);
It looks like you created a dependency on a web resource that doesn't turn on because you didn't ask for it. It only works on the first page because another control on the first page also needs it.
So, before you can continue, you need to know which web resource you need, and then enable it yourself. The only problem with this solution is that you are using a web resource that is not under your control. Therefore, if you yourself can write it.
source share