with ASP.NET WebAPI 2.0 we could abe to manage documentation of API using HelpPage. Is this feature continuing with ASP.NET Core or has introduced new approach to achieve this?
There is much better alternative called "Swashbuckle.Swagger". It's excellent and being using it for more than year for Web API 2 as well as ASP.NET Core Web API.
For more details Read this article
Related
Can anyone please help me by providing some learning material or any link for the step by step implementation of caching in .net core web API?
We have a web application built using ASP .NET 4.5 Webforms stack and based on MVP Pattern.
We are currently in the process of making certain aspects of the application service-oriented
which can then be used to serve the relevant content to third party clients.
Rather than doing a major overhaul, one of the options we are looking out is exposing this as WebAPI endpoints. Is anyone aware of codeplex/github hosted sample projects demonstrating the use of WebAPI ends points with MVP based webforms application? Any suggestions/insight/ recommendations would be helpful? Thanks.
A sample using Web Forms + Web API can be found here:
http://aspnet.codeplex.com/sourcecontrol/latest#Samples/WebApi/WebFormSample/ReadMe.txt
Greetings,
I'm confused as to the best approach to make when consuming REST based web services with .Net. At the moment I'm using the System.net.webclient class. Should I be using Webresponse, webrequest classes in System.Net ?
If I were to use another approach (Other than webclient) what disadvantages / advantages would I gain ?
Thanks,
If you use the WCF REST starter kit, there's pretty much no technical downside. There's a learning curve, however, and it will only work if you have .Net 3.5 SP1 (so I guess that's the down side).
You can also see this link if you want to do it without WCF.
I wanted to get some thoughts about API access either through WCF or MVC. Either works, but I like the idea of using MVC to build custom routes. I know this is possible with WCF (maintaining the request routes), but aside form the security disadvantages of not using WCF (which are not deal breakers) what other thoughts does the community have regarding this.
I have a project where we have been discussion using MVC or WCF and we are comfortable with both, but we are swaying towards MVC.
You should use the new ASP.Net MVC Web API framework, new to MVC 4.0.
I think MVC makes a great web API. I did this not too long ago for an android app that uses a RESTful web API using MVC 3. Here's a good tutorial:
http://msdn.microsoft.com/en-us/magazine/dd943053.aspx
If you're feeling adventurous check out the Web API framework included in MVC 4. NOTE: I have not experimented with this yet but plan to in the near future. See here: http://www.asp.net/web-api
I am going to start new MVC 3.0 .NET 4.0 application.
I want to implement each component for my web site once and simply reuse it then for another web sites i going to build.
Currently i am looking the best practice i can use to achieve my goal.
I did some research and found that I may get a lot of advantages using MEF.
I found interesting MEF MVC solution called plugable MVC http://www.thegecko.org/index.php/2010/06/pluggable-mvc-2-0-using-mef-and-strongly-typed-views.
Is it really worth to use such kind of approach(Plugabble MVC) of building MVC apps?
Advantages disadvantages of pluggable MVC?
May be somebody may suggest something else?
What specific problem are you trying to solve? MVC is a very extensible and pluggable framework as it is. I would say that for a simple site MEF is not necessary. Please provide more information on the issues you are running into with the stock MVC framework.