ASP.NET MVC 4 and the Web API: Building a REST Service from Start to Finish
- Used Book in Good Condition
This one hundred page book focuses exclusively on how you can best use the ASP.NET MVC 4 Framework to build world-class REST services using the Web API. It sets aside much of what the ASP.NET MVC Framework can do, and focuses exclusively on how the Web API can help you build web services. You will not find any help on CSS, HTML, JavaScript, or jQuery. Nor will you find any help on the Razor view engine, HTML Helpers, or model binding. If you need this information then Pro ASP.NET MVC 4 is yo
List Price: $ 19.99
Price: $ 12.21
[wprebay kw=”web+design+tutorial” num=”0″ ebcat=”-1″] [wprebay kw=”web+design+tutorial” num=”1″ ebcat=”-1″]
Way too much noise,
So begins page 103, the first page of the last chapter of this 125 page book. So what, you might wonder, did the previous 102 pages contain? The book starts with a great and needed introduction of REST, but then degenerates into page after page of setting up NHibernate mappings, dependency injection, security and authentication, and, I kid you not, Log4Net logging. Page after page that could, and should have been used to show the ins and outs of the Web API, modeling a UI to utilize the RESTful links that are supposed to drive your application, crafting AJAX requests for PUT and DELETE, etc, etc, were instead used to fill up reams and reams of Log4Net XML setup, and DI mappings.
I really wanted to give this book one star, but the REST introduction was actually quite good.
Other than that though this book desperately needed someone to keep the author on track, and focused on what the book was supposed to be about: using the Web API.
0
Was this review helpful to you?
|Don’t buy if you want to learn about the Web API,
* Using and configuration of NHibernate – not related to Web API
* Dependency Injection – not related to Web API
* Log4Net for logging – not related to Web API. If you have been coding for any amount of time you have your own logging tool.
* Using the ASP.NET Security role provider – could have filled this section with actual info on the Web API. If you have been doing ASP.NET for any amount of time you already know how to use the ASP.NET Security model.
You will spend most of your time learning about the authors favorite O/RM tools, Dependency Injection libraries and logging tools and how to configure them.
You WILL NOT learn how to make REST calls using Ajax. I was looking to learning how to perform basic CRUD using a REST service without all the extraneous tools the authors covers.
If you are looking to actually learn to use the Web API. DO NOT buy this book I repeat DO NOT by this book. You will not get a proper coverage of the Web API.
0
Was this review helpful to you?
|Generous Today,
But there’s more – consider the array of complex libraries hauled into the VS solution including NHibernate, Ninject, log4net, MVC Web API and you have to wonder how much coverage could you hope to get on the theoretical subject of the book. Entire chunks of those precious 125 pages are gobbled up with superficial treatment of important topics like DI and ORM (done the NHibernate way with POCO classes). The result is intellectual whiplash. If you read the brilliant DI classic by Mark Seeman, you can see how important topics like DI get proper treatment. DI flies by in this book in the wink of an eye. The same short shrift gets applied to NHib, Ninject and so on.
BTW, any hope you may have regarding coding along with the author should be abandoned straight away. The book is simply not structured that way. Consider the book to be extended source code comments, not step-wise instructions.
In the prologue to the book (a must read), a friend of the author describes a production meltdown hellscape complete with all the usual suspects running in circles with their aprons over there faces, arms flailing. Into the breach steps the author, Mountain Dew can in hand, nowhere better to go, and nothing but coding bravado coursing through his teenage veins. I fear that the same undisciplined approach evident in this anecdote was applied to the production of this book. Perhaps the author simple bit off way to much and could not meet the demands of publishing a well-rounded treatise.
I generously gave the book 3 stars since the sample application is very well crafted and the author does know what he’s doing at a keyboard and whiteboard. I might be able to mine a few nuggets from the source code but it would have been nice to have a detailed discussion to go along with it.
0
Was this review helpful to you?
|