Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ScriptManager and debug=false

ScriptManager and debug=false

Scheduled Pinned Locked Moved Web Development
javascripthelpannouncementcsharpasp-net
2 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • G Offline
    G Offline
    Gennady Oster
    wrote on last edited by
    #1

    Hi there ! I cannot persuade ScriptManager control to switch MicrosoftAjax js library to the release version when the web.config defines debug=false. Maximum that it can do for me - load both versions simultaniously :(( . I had to refuse to use the built-in resources because of known bug (http://weblogs.asp.net/bleroy/archive/2007/01/31/how-to-work-around-the-quot-access-denied-quot-cross-domain-frame-issue-in-asp-net-ajax-1-0.aspx[^]) Here is how my ScriptManager control looks like: <asp:ScriptManager ID="ScriptManager1" runat="server" EnablePageMethods="True" EnableViewState="False" > <Scripts> <asp:ScriptReference Name="MicrosoftAjax.js" Path="javascript/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.js" /> <asp:ScriptReference Name="MicrosoftAjax.debug.js" Path="javascript/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.debug.js" /> </Scripts> </asp:ScriptManager> I'll be very thankful to anybody that can shed light on this mystery. Thanks in advance. Regards, Gennady

    G 1 Reply Last reply
    0
    • G Gennady Oster

      Hi there ! I cannot persuade ScriptManager control to switch MicrosoftAjax js library to the release version when the web.config defines debug=false. Maximum that it can do for me - load both versions simultaniously :(( . I had to refuse to use the built-in resources because of known bug (http://weblogs.asp.net/bleroy/archive/2007/01/31/how-to-work-around-the-quot-access-denied-quot-cross-domain-frame-issue-in-asp-net-ajax-1-0.aspx[^]) Here is how my ScriptManager control looks like: <asp:ScriptManager ID="ScriptManager1" runat="server" EnablePageMethods="True" EnableViewState="False" > <Scripts> <asp:ScriptReference Name="MicrosoftAjax.js" Path="javascript/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.js" /> <asp:ScriptReference Name="MicrosoftAjax.debug.js" Path="javascript/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.debug.js" /> </Scripts> </asp:ScriptManager> I'll be very thankful to anybody that can shed light on this mystery. Thanks in advance. Regards, Gennady

      G Offline
      G Offline
      Gennady Oster
      wrote on last edited by
      #2

      As usual, sending question I continued to think about it. And suddenly I've understand what was my mistake. I don't need to include both script referencies - only one to release version. ScriptManager is smart enough to add "debug" to the name and key, if in debug mode. Sorry. Regards, Gennady

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups