Been using the toolkit for years, but today I installed it on a new domain. I used NuGet to install it. Production environment is asp.net 4.0. Development tool is VS2012. Installed version is 7.1213.
I add the register assembly page directive. There's no problem with that. I then add a ToolkitScriptManager and run the page. It immediately crashes displaying the following error:
The requested script resource 'Seadragon.Seadragon.Config.js' requires version 'AjaxControlToolkit, Version=4.1.7.1213, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' of the ASP.NET AJAX Framework. To use this resource, make sure that the application references version 'AjaxControlToolkit, Version=4.1.7.1213, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e'.
How do I fix this?
Comments: This issue has been resolved. I had not noticed, but my VS2012 toolbox showed an AJAX Toolkit tab with tools, even after removing the Toolkit completely. So obviously, the tools were linked to a different installation than the one I was working in. I removed the tab, created a new one, and right clicked to 'Choose Items'. I browsed to the .dll for the correct project, and clicked ok. The tools installed and now add the ToolScriptManager no longer created the error. All components are working correctly. //tom
I add the register assembly page directive. There's no problem with that. I then add a ToolkitScriptManager and run the page. It immediately crashes displaying the following error:
The requested script resource 'Seadragon.Seadragon.Config.js' requires version 'AjaxControlToolkit, Version=4.1.7.1213, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e' of the ASP.NET AJAX Framework. To use this resource, make sure that the application references version 'AjaxControlToolkit, Version=4.1.7.1213, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e'.
How do I fix this?
Comments: This issue has been resolved. I had not noticed, but my VS2012 toolbox showed an AJAX Toolkit tab with tools, even after removing the Toolkit completely. So obviously, the tools were linked to a different installation than the one I was working in. I removed the tab, created a new one, and right clicked to 'Choose Items'. I browsed to the .dll for the correct project, and clicked ok. The tools installed and now add the ToolScriptManager no longer created the error. All components are working correctly. //tom