• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 545
  • Last Modified:

Why is MicrosoftAjax.en-US.js expected when MicrosoftAjax.js specified

Even though in my test page the MicrosoftAjax.js is included in the path, it returns an error saying "Sys" is undefined"... View source of the page shows that somehow MicrosoftAjax.en-US.js  is in the path.

<asp:ScriptManager ID="ScriptManager1" runat="server"  >
        <Scripts>
            <asp:ScriptReference Name="MicrosoftAjax.js" ScriptMode="Auto" Path="MicrosoftAjaxLibrary/System.Web.Extensions/3.5.0.0/3.5.30729.1/MicrosoftAjax.js" />
            <asp:ScriptReference Name="MicrosoftAjaxWebForms.js" ScriptMode="Auto" Path="MicrosoftAjaxLibrary/System.Web.Extensions/3.5.0.0/3.5.30729.1/MicrosoftAjaxWebForms.js" />
        </Scripts>
</asp:ScriptManager>

 

 I made a copy of  /MicrosoftAjax.js" &  MicrosoftAjaxWebForms.js and called it MicrosoftAjax.en-US.js & MicrosoftAjaxWebForms.en-US.js in the same location and now it works.
I'm not sure why this is and what the ramifications are if I move this to production.  Any suggestions?
0
nicholsf
Asked:
nicholsf
1 Solution
 
nicholsfAuthor Commented:
Setting  EnableScriptLocalization="false"  in the ScriptManager Tag fixed the problem
<asp:ScriptManager ID="ScriptManager1" runat="server" EnableScriptLocalization="false" >
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now