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.
xmlhttprequest aspnetboilerplate
edited Nov 6 at 5:43
JohnB
882715
asked Nov 5 at 17:00
user3795496
133
add a comment |
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.
xmlhttprequest aspnetboilerplate
edited Nov 6 at 5:43
JohnB
882715
asked Nov 5 at 17:00
user3795496
133
add a comment |
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.
xmlhttprequest aspnetboilerplate
edited Nov 6 at 5:43
JohnB
882715
asked Nov 5 at 17:00
user3795496
133
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
xmlhttprequest aspnetboilerplate
edited Nov 6 at 5:43
JohnB
882715
asked Nov 5 at 17:00
user3795496
133
edited Nov 6 at 5:43
JohnB
882715
asked Nov 5 at 17:00
user3795496
133
edited Nov 6 at 5:43
JohnB
882715
edited Nov 6 at 5:43
JohnB
882715
edited Nov 6 at 5:43
JohnB
882715
882715
asked Nov 5 at 17:00
user3795496
133
asked Nov 5 at 17:00
user3795496
133
asked Nov 5 at 17:00
user3795496
133
133
add a comment |
add a comment |
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;
answered Nov 6 at 4:55
aaron
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
add a comment |
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;
answered Nov 6 at 4:55
aaron
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
add a comment |
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;
answered Nov 6 at 4:55
aaron
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
add a comment |
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;
answered Nov 6 at 4:55
aaron
7,90331129
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;
answered Nov 6 at 4:55
aaron
7,90331129
answered Nov 6 at 4:55
aaron
7,90331129
answered Nov 6 at 4:55
aaron
7,90331129
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
add a comment |
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
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
