I've got a question related to /js and /jsdebug. We've got one specific server running a CMS, which "only" supports .NET 3.5. Most of the time everything works fine: We've got our /js webservice-proxy, which is included by the service-reference of the scriptmanager.
Unfortunately newly sometimes occurs an error: The scriptmanager still generates the script-link to /js, but the WCF-service only offers /jsdebug anymore (without any changes). As soon as we recycle the app-pool of the web everything works fine again
- until the next time (which occurs between every 6 or 48 hours).
Anyone an idea what could cause that behaviour? Or does anyone at least know how to force the WCF-service to always use the /js endpoint? Will it be sufficient to insert "js" at the address attribute of the endpoint (instead of leaving it empty?).
Thanks and have a nice day!
View Complete Post