If you have control over the code-behind, you can register the JavaScript to run at startup via something like: this.Page.ClientScript.RegisterStartupScript( this.GetType(), “StartupScript”, “Sys.Application.add_load(function() { functioncall(); });”, true); As long as your component has been loaded via Sys.Application.add_init() you should be fine…
I have seen this error in a web application that was upgraded from a Visual Studio 2005 project to a Visual Studio 2010 project. The solution was to remove the following section from the web.config file: <runtime> <assemblyBinding xmlns=”urn:schemas-microsoft-com:asm.v1″> <dependentAssembly> <assemblyIdentity name=”System.Web.Extensions” publicKeyToken=”31bf3856ad364e35″/> <bindingRedirect oldVersion=”1.0.0.0-1.1.0.0″ newVersion=”3.5.0.0″/> </dependentAssembly> <dependentAssembly> <assemblyIdentity name=”System.Web.Extensions.Design” publicKeyToken=”31bf3856ad364e35″/> <bindingRedirect oldVersion=”1.0.0.0-1.1.0.0″ newVersion=”3.5.0.0″/> </dependentAssembly> … Read more