Microsoft Silverlight Books

Good introduction to rest with .net

Good introduction to rest with .net. I'm a WCF dev so I can say that this book helps me a lot to design out rest API for our services consumers

Luis Rojas Mendez
05 November, 2010

Example code is written as ....CONSOLE APPS?!?

This may be the worst programming book I've ever bought. After reading through the first four chapters, I still didn't find a end to end code example that you could dig into and explore. I believe that most programmers learn by example, and the examples in this book are horrible. After finding the woeful examples presented in the book lacking, I downloaded the complete sample code only to find that they are written as CONSOLE APPLICATIONS. That's totally useless. The examples need to be refactored to run in an IIS context.

R. Flippo
15 April, 2010

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009

Well written; however, bad example code and too little focus on the client

I like the way the author writes; however, I have a few problems with the book as a whole:
- The example code is a mess. It's badly formatted and a lot of just doesn't work. If you don't believe me, download it yourself before buying the book: [...]
- There is just not enough focus on the client (the book contains 11 chapters and chapter 10 is client code). However, the example must have been an academic exercise for the author who focused on SSDS rather than a simpler example. He would have been better off sticking to his example code and focusing more on security from the client's perceptive.



D. Yates
15 October, 2009