Do you want to use AJAXControltoolkit 4 ? Are you stuck with following error occurred when you run your code
Error Message:
Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "AjaxControlToolkit.Properties.Resources.NET4.resources" was correctly embedded or linked into assembly "AjaxControlToolkit" at compile time, or that all the satellite assemblies required are loadable and fully signed.
Cause:
This error occurred when An unhandled exception was generated during the execution of the current web request, basically when you use any AJAX control but does not refer a ajax library in your page then Ajaxcontoltoolkit unable to load reference of that control from System.Qeb.UI.Contol namespace and hence it produce such error
Resolutions
Add "Script Manager" in ASPX page as below
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
<cc1:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server"> </cc1:ToolkitScriptManager>
OR
<asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
Hope it Helps to resolve the issue
Error Message:
Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "AjaxControlToolkit.Properties.Resources.NET4.resources" was correctly embedded or linked into assembly "AjaxControlToolkit" at compile time, or that all the satellite assemblies required are loadable and fully signed.
Cause:
This error occurred when An unhandled exception was generated during the execution of the current web request, basically when you use any AJAX control but does not refer a ajax library in your page then Ajaxcontoltoolkit unable to load reference of that control from System.Qeb.UI.Contol namespace and hence it produce such error
Resolutions
Add "Script Manager" in ASPX page as below
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
<cc1:ToolkitScriptManager ID="ToolkitScriptManager1" runat="server"> </cc1:ToolkitScriptManager>
OR
<asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
Hope it Helps to resolve the issue
No comments:
Post a Comment