UnobtrusiveValidationMode

4 posts, 0 answers
  1. Cavit
    Cavit avatar
    16 posts
    Member since:
    Apr 2015

    Posted 07 Sep 2015 Link to this post

    Hi,

    I have upgraded the Telerik version from 2014.1 to 2015.2. Now getting an error for Jquery. As I found there are two multiple solutions:

    1) Disable the UnobtrusiveValidationMode

    2) Add definition for JQuery in global.asax.

     

    If I choose the first option, will it affect any new functionality I will get from 2015.2 ? Which one do you recommend ?

     

    Regards

  2. Cavit
    Cavit avatar
    16 posts
    Member since:
    Apr 2015

    Posted 07 Sep 2015 in reply to Cavit Link to this post

    Addition to that, which jquery version is used in 2015.2 ?
  3. UI for ASP.NET Ajax is Ready for VS 2017
  4. Marin Bratanov
    Admin
    Marin Bratanov avatar
    3602 posts

    Posted 08 Sep 2015 Link to this post

    Hi Cavit,

    Our controls do not rely on the validation mode of the page, so disabling the Unobtrusive validation will not affect the UI for ASP.NET AJAX tools.

    If you intend to use the Unobtrusive validation with our controls, however, I advise that you follow this article: http://docs.telerik.com/devtools/aspnet-ajax/general-information/troubleshooting/jquery-troubleshooting.

    As for the jQuery version in Q2 2015 - it uses 1.11.1, as listed in the following article: http://docs.telerik.com/devtools/aspnet-ajax/general-information/using-jquery/using-jquery#jquery-version-history-in-telerik-ui-controls.

    Regards,

    Marin Bratanov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  5. Cavit
    Cavit avatar
    16 posts
    Member since:
    Apr 2015

    Posted 10 Sep 2015 Link to this post

    Thanks Martin,

    I will disable UnobtrusiveValidationMode to avoid breaking the inline js. I  am curious why this issue is surfaced now when I want to upgrade from 2014.1 to 2015.2 ? I didn't have this problem before.

     

Back to Top