asp.net-web-api2

my web api like public async Task<IHttpActionResult> RegisterUser(User user) { //User Implementation here return Ok(user); } I am using HTTPClient to request web api as mentioned below. var client = new HttpClient(); string json = JsonConvert.SerializeObject(model); var result = await client.PostAsync( "api/users", new StringContent(json, Encoding.UTF8, "application/json")); Where i can find user object in my result request which is implemented on client application? You can use (depands on what you need), and de-serialize it back to user object. await result.Content.ReadAsByteArrayAsync(); /

I currently have a Web API that implements a RESTFul API. The model for my API looks like this: public class Member { public string FirstName { get; set; } public string LastName { get; set; } public DateTime Created { get; set; } public DateTime BirthDate { get; set; } public bool IsDeleted { get; set; } } I've implemented a PUT method for updating a row similar to this (for brevity, I've omitted some non-relevant stuff): [Route("{id}")] [HttpPut] public async System.Threading.Tasks.Task<HttpResponseMessage> UpdateRow(int id, [FromBody]Models.Member model) { // Do some error checking // ... /

I need help how to think about designing our application to fit into the new Azure Service Fabric template. Today we have an application built on Azure Cloud Services. The application is built around DDD and we have separate bounded contexts for different subsystem parts of the application. The bounded contexts are today hosted in one worker role that exposes these subsystems using a single WebAPI. Additionally we have one Web Role hosting the web frontend and one Worker Role processing a background queue. We strive to move to a micro services architecture. The first thing I planned to do was

I have a WebAPI 2 / AngularJS SPA application that uses Identity 2 for authentication. Locally my code stores a token for authentication. I would like to implement functionality that allows my application to request additional javascript for authenticated users after my initial index.html page has been downloaded. Is there a way I can make my server code give out the javascript files to only authenticated and authorized users? Something similar to the way a controller action method returns data to only authenticated and authorized users. Dalorzo You can force the static files to go through the

I have an ASP.NET WEB-API 2 app witch needs to have a POST method that accepts a JOSN string with unknown structure from javascript . I enabled cors and GET methods works fine, however when sending JSON from the client the api's method parameter is always null . This is my api method: //parameters i tried: //[FromBody]string model //[FromBody]dynamic model //dynamic model public HttpResponseMessage Post(string model) { return new HttpResponseMessage() { Content = new StringContent("POST: Test message: " + model) }; } and my client method: function sendRequest() { var Test = {"Name":"some name"

So, using the ODataController , you get to control what gets returned if somebody does /odata/Foos(42)/Bars , because you'll be called on the FoosController like so: public IQueryable<Bar> GetBars([FromODataUri] int key) { } But what if you want to control what gets returned when somebody does /odata/Foos?$expand=Bars ? How do you deal with that? It triggers this method: public IQueryable<Foo> GetFoos() { } And I assume it just does an .Include("Bars") on the IQueryable<Foo> that you return, so... how do I get more control? In particular, how do I do it in such a way that OData doesn't break

I'm new to ASP.NET but I'm looking to implement some versioning for a new API I'm about to start. I'm not even sure if what I'm looking for is possible but I'm after a very clean version method using a header variable. Ideally I want to be able to have a versions folder within the code structure and different folders containing the different API versions within that. Each version folder would contain a full copy of the core API code so I'd know there would never be any conflicts etc. I know this would inflate the code but it's worth to keep it very clean and there would only be over 2-3