3
I came across the need to consume an ASMX Web Service. Until then I had only consumed Restful Apis. I noticed that the same is very different from a Restful API, for example.
Given the way it is configured, it seems that the same has already been left aside, which is something quite old.
Is it recommended to use an ASMX Web Service? Does anyone still use it to create a Web Service from scratch?
3
Define obsolete.
If you consider that it is used for ASP.NET Classic, with Webforms and things like that, we can say yes.
But it is still considered a valid and supported component in .NET. You can use..
The question is whether it should. There are no updates upon it, and there is a general, not exactly official recommendation not to use it anymore.
Who has a large base using it can have some gain while maintaining continuity. If you will only consume what already exists, it can be interesting.
If there is little thing and it is easy to convert I think I would go from Web API using ASP.NET Core. Only you can evaluate whether it compensates the effort. The gain will not be great in use, perhaps more organization in development, or in scale.
Browser other questions tagged .net asp.net web-service api rest
You are not signed in. Login or sign up in order to post.
Given what you said, about ASP.NET Core and, adding that it has been a great success since release along with community support, would it be correct to say that it is currently better to create an ASP.NET Core API than ASMX? I see no explanation for using an old technology that is probably only available due to the large number of applications that use it.
– perozzo
Yes, it’s much better.
– Maniero