Upgrading 2.x to 3.x With Task Methods which end in -Async for Asp.Net Boilerplate











up vote
0
down vote

favorite












I have found that my legacy services which have a method name that follows:




public Task SomeMethodNameAsync(...)




Has the API signature




service.someMethodName(...)




for the UI to make XHR requests to. Essentially, the upgrade is forcing us to change ALL of our APIs which have that signature.



My question is whether this is a documented feature, or, if there is a flag somewhere (which I haven't found via Google) for disabling this renaming of the API.










share|improve this question




























    up vote
    0
    down vote

    favorite












    I have found that my legacy services which have a method name that follows:




    public Task SomeMethodNameAsync(...)




    Has the API signature




    service.someMethodName(...)




    for the UI to make XHR requests to. Essentially, the upgrade is forcing us to change ALL of our APIs which have that signature.



    My question is whether this is a documented feature, or, if there is a flag somewhere (which I haven't found via Google) for disabling this renaming of the API.










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I have found that my legacy services which have a method name that follows:




      public Task SomeMethodNameAsync(...)




      Has the API signature




      service.someMethodName(...)




      for the UI to make XHR requests to. Essentially, the upgrade is forcing us to change ALL of our APIs which have that signature.



      My question is whether this is a documented feature, or, if there is a flag somewhere (which I haven't found via Google) for disabling this renaming of the API.










      share|improve this question















      I have found that my legacy services which have a method name that follows:




      public Task SomeMethodNameAsync(...)




      Has the API signature




      service.someMethodName(...)




      for the UI to make XHR requests to. Essentially, the upgrade is forcing us to change ALL of our APIs which have that signature.



      My question is whether this is a documented feature, or, if there is a flag somewhere (which I haven't found via Google) for disabling this renaming of the API.







      xmlhttprequest aspnetboilerplate






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 6 at 5:43









      JohnB

      882715




      882715










      asked Nov 5 at 17:00









      user3795496

      133




      133
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          The feature is listed as a breaking change in v3.2.0.



          It doesn't change the actual endpoint for XHR requests, just the jQuery proxy.



          To disable the renaming, configure this in the PreInitialize method of your *.Web.Core module:



          Configuration.Modules.AbpWebCommon().ApiProxyScripting.RemoveAsyncPostfixOnProxyGeneration = false;





          share|improve this answer





















          • Thank you very much! It worked as described! I need to go back and practice my google-fu :(
            – user3795496
            Nov 6 at 14:29











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














           

          draft saved


          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53158908%2fupgrading-2-x-to-3-x-with-task-methods-which-end-in-async-for-asp-net-boilerpla%23new-answer', 'question_page');
          }
          );

          Post as a guest
































          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote



          accepted










          The feature is listed as a breaking change in v3.2.0.



          It doesn't change the actual endpoint for XHR requests, just the jQuery proxy.



          To disable the renaming, configure this in the PreInitialize method of your *.Web.Core module:



          Configuration.Modules.AbpWebCommon().ApiProxyScripting.RemoveAsyncPostfixOnProxyGeneration = false;





          share|improve this answer





















          • Thank you very much! It worked as described! I need to go back and practice my google-fu :(
            – user3795496
            Nov 6 at 14:29















          up vote
          0
          down vote



          accepted










          The feature is listed as a breaking change in v3.2.0.



          It doesn't change the actual endpoint for XHR requests, just the jQuery proxy.



          To disable the renaming, configure this in the PreInitialize method of your *.Web.Core module:



          Configuration.Modules.AbpWebCommon().ApiProxyScripting.RemoveAsyncPostfixOnProxyGeneration = false;





          share|improve this answer





















          • Thank you very much! It worked as described! I need to go back and practice my google-fu :(
            – user3795496
            Nov 6 at 14:29













          up vote
          0
          down vote



          accepted







          up vote
          0
          down vote



          accepted






          The feature is listed as a breaking change in v3.2.0.



          It doesn't change the actual endpoint for XHR requests, just the jQuery proxy.



          To disable the renaming, configure this in the PreInitialize method of your *.Web.Core module:



          Configuration.Modules.AbpWebCommon().ApiProxyScripting.RemoveAsyncPostfixOnProxyGeneration = false;





          share|improve this answer












          The feature is listed as a breaking change in v3.2.0.



          It doesn't change the actual endpoint for XHR requests, just the jQuery proxy.



          To disable the renaming, configure this in the PreInitialize method of your *.Web.Core module:



          Configuration.Modules.AbpWebCommon().ApiProxyScripting.RemoveAsyncPostfixOnProxyGeneration = false;






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 6 at 4:55









          aaron

          7,90331129




          7,90331129












          • Thank you very much! It worked as described! I need to go back and practice my google-fu :(
            – user3795496
            Nov 6 at 14:29


















          • Thank you very much! It worked as described! I need to go back and practice my google-fu :(
            – user3795496
            Nov 6 at 14:29
















          Thank you very much! It worked as described! I need to go back and practice my google-fu :(
          – user3795496
          Nov 6 at 14:29




          Thank you very much! It worked as described! I need to go back and practice my google-fu :(
          – user3795496
          Nov 6 at 14:29


















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53158908%2fupgrading-2-x-to-3-x-with-task-methods-which-end-in-async-for-asp-net-boilerpla%23new-answer', 'question_page');
          }
          );

          Post as a guest




















































































          這個網誌中的熱門文章

          Xamarin.form Move up view when keyboard appear

          Post-Redirect-Get with Spring WebFlux and Thymeleaf

          Anylogic : not able to use stopDelay()