Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Unfortunately the ScriptResourceMapping is required. However, with a bit of work you can remove the reference from the ScriptManager so it won't render jQuery again.</p> <p>Create your own class that derives from ScriptManager in your web project:</p> <pre><code>using System; using System.Linq; using System.Web.UI; namespace WebApplication46 { public class CustomScriptManager : ScriptManager { protected override void OnInit(EventArgs e) { Page.PreRenderComplete += Page_PreRenderComplete; base.OnInit(e); } private void Page_PreRenderComplete(object sender, EventArgs e) { var jqueryReferences = Scripts.Where(s =&gt; s.Name.Equals("jquery", StringComparison.OrdinalIgnoreCase)).ToList(); if (jqueryReferences.Count &gt; 0) { // Remove the jquery references as we're rendering it manually in the master page &lt;head&gt; foreach (var reference in jqueryReferences) { Scripts.Remove(reference); } } } } } </code></pre> <p>Next, configure a tagMapping entry in your web.config so that ASP.NET will use your custom ScriptManager instead of the one in the box:</p> <pre><code>&lt;system.web&gt; &lt;pages&gt; &lt;tagMapping&gt; &lt;add tagType="System.Web.UI.ScriptManager" mappedTagType="WebApplication46.CustomScriptManager" /&gt; &lt;/tagMapping&gt; &lt;/pages&gt; &lt;/system.web&gt; </code></pre> <p>That's it. Now your CustomScriptManager will ensure all jQuery references are removed from itself before the ScriptManager has a chance to start its rendering logic and you'll still satisfy all the requirements for UnobtrusiveValidation to work (assuming you have a reference to jQuery in your page's tag).</p>
    singulars
    1. This table or related slice is empty.
    1. POasp.net 4.5 Web Forms Unobtrusive Validation jQuery Issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USDamian Edwards
    1. USDamian Edwards
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your suggestion, I completely missed it when you posted it. Just taking another look at some of the 4.5 features. I tried your suggestion, tested in Firefox, Chrome and IE and each result is the same - the header scripts break because of the 2nd jquery reference. Looks like I won't be able to use unobtrusive validation without major revisions to my webforms apps. I'd love to find a way to override this behavior. Is this possible in an update to webforms? Or would we need to wait for the next version of asp.net?
      singulars
      1. PO
      1. USJohn
    2. COI just want to clarify because my comment above is misleading. Damian, your solution works perfectly (my previous comment was from an earlier approach that you posted). I've been using it in an application and it solved my problem. I'd still love to see a built in solution for this in a future version of WebForms, but in lieu of that, your workaround is much appreciated.
      singulars
      1. PO
      1. USJohn
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload