Rating: 
Summary: Not worth your money
Review: I read this book from cover to cover. This book [is bad] in a lot of ways, first it contains loads of errors. Lot of codes for the labs WILL NOT WORK. This is my first time MS book purchase so i donot know how often it happens. second it does not cover lot of stuff that is on the exam. Very little is talked about ADO.NET, far from enough. Also for class directives. This book only list some of the names for the page class property/method, w/o further discussion. You have to go to msdn to find all the stuff that will make sense. Looks like MS publishes this book to mislead people so nobody can get passed.
The only thing good about this book is the structure is well laid out. You can get a general idea about what .net web application development is about from reading this book. But this book is far short from test preparation. The CD issue does not bother me much, you can get the .mdb file from the CD. get the password and there is a table contains all the correct answers. cmon guys you are preparing MCSD so i know y'all can do this. But it does not have explainations and 50 easy questions wont prepare you for the exam.
Rating:
Summary: disappointing
Review: I regret buying this book. It has been very frustrating to use. There are frequently small bits of code missing which result in things not working as they should, if at all. I know enough (from OTHER ASP.NET books) to have a general idea of what is wrong, but it is still quite frustrating. I've been particularly disappointed by the ADO.NET chapter. I wanted to use this book as a study resource to prepare for the MCAD web apps certification exam, which the book is supposedly a training kit for. Instead I feel I've wasted time and money. I'm just glad I didn't pay full price. Personally, I recommend Stephen Walther's ASP.NET Unleashed and the O'Reilly ASP.NET Nutshell book. Both are much better.
Rating: 
Summary: Not a bad prep book after all
Review: I think the book does the job it was written for---to prepare you for an exam. It's not meant to be a primer as you need to be familiar with C#.NET or VB.NET to fully understand what's going on. You definitely need to get some hands-on practice and read other ASP.NET/ADO.NET/etc books, but given the task of tutoring you it. deserves its five stars.
Rating: 
Summary: Just took the beta exam.
Review: I used this book almost exclusively to prepare for the beta exam (along with MSDN). Overall I'd say the book does a pretty good job of preparing you. If you really want to be sure I'd get ADO.NET, ASP.NET, and XML book(s) to complement it. I didn't have time to run through all the labs, but the ones I did do worked just fine. The test-prep software does have good questions, but (as other posters have mentioned) it doesn't give any feedback about if you got the question right or wrong. If you are not used to MCP exams, I'd purchase some 'third party' test-prep software also. It is a gigantic leap forward for a MS-Press book. I've never been a fan on MS-Press's 'Test Prep' books, but this one can legitimately compete 'third party' books.
Rating: 
Summary: Keeping it Real
Review: I usually enjoy MS Press titles, but this one was miserable. Other reviewers have mentioned the plethora of shoddy, uncompilable code, so I won't bother to mention any examples. It is worth noting, I suppose, that the VB.NET examples are in somewhat better shape than the C# examples because the authors apparently wrote their examples in VB.NET, but translated to C# without ever compiling, much less testing, their translation. How such a terrible mess could have slipped out the MS-Press door is quite beyond me. If you are technically astute and comfortable with C#, you can probably debug your way through the sample code and derive some benefit from the book. But then we get to area where this book falls down completely: the authors seem to be completely clueless with regard to sound software design. As a service to readers, let me offer some insights into where the book misses the mark so that your code will not similarly go astray: 1. The authors describe abstract classes and interfaces, but do not describe why you would use one or the other. Of course, the key differentiator that the authors miss is that an abstract class can include default implementations of methods. Here's a rule of thumb: if derived classes can piggyback on an implementation of a common base method or methods, put the common code in an abstract class. Otherwise, use an interface. 2. The authors explain that you cannot derive a web form from another web form (i.e., there is no visual inheritance). This is true enough, but many shops, including my customers when I was an MS consultant, plus the one where I now work, use a Page-derived base class from which all page classes inherit. This allows you to provide common functionality across all the pages in your site. 3. On page 157, the authors would have us iterate through a RadioButtonList, check each one to see if it is checked, then perform some operation if it is. This is just dumb. A radio button list can have only one checked member, and it can be accessed by calling RadioButtonList.SelectedItem (or SelectedIndex or SelectedValue, depending on your situation). 4. On page 200, the page class sets stores "true" in ViewState["Changed"] in the TextBox_TextChanged event handler, then checks the value of ViewState["Changed"] in the butExit_Click event handler. Again, the code works, but it's really dumb. Both event handlers will get fired in the same postback, so you ought to give the class that implements the Page a boolean member variable with a default false value. When the TextChanged event fires, set the member variable to true. Then use the member variable in the butExit_Click method. Using ViewState in this situation is kind of like sending a package to your next-door neighbor via Fedex, rather than walking over and ringing his door bell. 5. On p. 254, the authors recommend instantiating a single database connection in global.asax and making it available for each user connection by setting a session variable in the Session_Start event handler. Supposedly, this design "conserves resources and makes it easier to maintain connection and adapter settings...." In fact, what this will do is make your web site scale miserably because every single user will have to wait in line while the others take turns sharing that single connection. **I cannot emphasize enough how bad this design is.** Windows servers have built in connection-pooling capabilities that do a great job of conserving resources while providing good scalability. Just instantiate a new connection for every database operation, and allow the Windows infrastructure to do its magic behind the scenes. And if you're smart, you'll do this in a class (or classes) in a distinctive logical tier that most designers call the data access layer. However, the three-tier (later n-tier) design revolution that swept through the Windows software world starting about 6 years ago seems to have completely escaped the notice of our authors. 6. On p. 261, the authors use a typed dataset with a type name of dsContacts. They also have a member variable with the name of dsContacts. Does anyone else see the potential for confusion here? 7. On p. 385, the authors recommend using user name as the primary key for a user table. The problems this database design will cause are severe. * When the second "John Smith" or "Mary Jones" tries to access your system, you'll get a database error. The only workaround is to get John or Mary to use a different name. Yeah, right. * Using a long string as a foreign key on other tables that reference the user table leads to inefficient space utilization and terrible performance when you do joins. Anybody who knows anything about database design knows that you set up some kind of guaranteed unique key, such as an auto-increment integer, and make name an attribute of the user. 8. The authors fail to note that if session state uses the sqlserver mode, session state will survive a reset when web.config is changed, so users will not be adversely affected. 9. On p. 408, the authors ignore the security implications of causing an authentication cookie to be written to a user's hard drive. This is a recipe for disaster for users who are accessing a web app from a public location (library, kiosk, Kinko's, etc.) because subsequent users will have access to their credentials by virtue of the authentication cookie already on the hard drive. Do your users a favor and set the createPersistentCookie parameter to false when you call RedirectFromLoginPage(). I could write a much lengthier list of "really dumb coding ideas" to accompany this list of really dumb design ideas, but space does not permit. So let me conclude by stating what should by now be obvious: if you have extensive experience with object-oriented web programming in a multi-tier design paradigm, but simply lack exposure to ASP.NET syntax, you can probably find something useful in this book. Otherwise, stay away!
Rating:
Summary: Atrocious Editing, Awful Design Recommendations
Review: I usually enjoy MS Press titles, but this one was miserable. Other reviewers have mentioned the plethora of shoddy, uncompilable code, so I won't bother to mention any examples. It is worth noting, I suppose, that the VB.NET examples are in somewhat better shape than the C# examples because the authors apparently wrote their examples in VB.NET, but translated to C# without ever compiling, much less testing, their translation. How such a terrible mess could have slipped out the MS-Press door is quite beyond me. If you are technically astute and comfortable with C#, you can probably debug your way through the sample code and derive some benefit from the book. But then we get to area where this book falls down completely: the authors seem to be completely clueless with regard to sound software design. As a service to readers, let me offer some insights into where the book misses the mark so that your code will not similarly go astray: 1. The authors describe abstract classes and interfaces, but do not describe why you would use one or the other. Of course, the key differentiator that the authors miss is that an abstract class can include default implementations of methods. Here's a rule of thumb: if derived classes can piggyback on an implementation of a common base method or methods, put the common code in an abstract class. Otherwise, use an interface. 2. The authors explain that you cannot derive a web form from another web form (i.e., there is no visual inheritance). This is true enough, but many shops, including my customers when I was an MS consultant, plus the one where I now work, use a Page-derived base class from which all page classes inherit. This allows you to provide common functionality across all the pages in your site. 3. On page 157, the authors would have us iterate through a RadioButtonList, check each one to see if it is checked, then perform some operation if it is. This is just dumb. A radio button list can have only one checked member, and it can be accessed by calling RadioButtonList.SelectedItem (or SelectedIndex or SelectedValue, depending on your situation). 4. On page 200, the page class sets stores "true" in ViewState["Changed"] in the TextBox_TextChanged event handler, then checks the value of ViewState["Changed"] in the butExit_Click event handler. Again, the code works, but it's really dumb. Both event handlers will get fired in the same postback, so you ought to give the class that implements the Page a boolean member variable with a default false value. When the TextChanged event fires, set the member variable to true. Then use the member variable in the butExit_Click method. Using ViewState in this situation is kind of like sending a package to your next-door neighbor via Fedex, rather than walking over and ringing his door bell. 5. On p. 254, the authors recommend instantiating a single database connection in global.asax and making it available for each user connection by setting a session variable in the Session_Start event handler. Supposedly, this design "conserves resources and makes it easier to maintain connection and adapter settings...." In fact, what this will do is make your web site scale miserably because every single user will have to wait in line while the others take turns sharing that single connection. **I cannot emphasize enough how bad this design is.** Windows servers have built in connection-pooling capabilities that do a great job of conserving resources while providing good scalability. Just instantiate a new connection for every database operation, and allow the Windows infrastructure to do its magic behind the scenes. And if you're smart, you'll do this in a class (or classes) in a distinctive logical tier that most designers call the data access layer. However, the three-tier (later n-tier) design revolution that swept through the Windows software world starting about 6 years ago seems to have completely escaped the notice of our authors. 6. On p. 261, the authors use a typed dataset with a type name of dsContacts. They also have a member variable with the name of dsContacts. Does anyone else see the potential for confusion here? 7. On p. 385, the authors recommend using user name as the primary key for a user table. The problems this database design will cause are severe. * When the second "John Smith" or "Mary Jones" tries to access your system, you'll get a database error. The only workaround is to get John or Mary to use a different name. Yeah, right. * Using a long string as a foreign key on other tables that reference the user table leads to inefficient space utilization and terrible performance when you do joins. Anybody who knows anything about database design knows that you set up some kind of guaranteed unique key, such as an auto-increment integer, and make name an attribute of the user. 8. The authors fail to note that if session state uses the sqlserver mode, session state will survive a reset when web.config is changed, so users will not be adversely affected. 9. On p. 408, the authors ignore the security implications of causing an authentication cookie to be written to a user's hard drive. This is a recipe for disaster for users who are accessing a web app from a public location (library, kiosk, Kinko's, etc.) because subsequent users will have access to their credentials by virtue of the authentication cookie already on the hard drive. Do your users a favor and set the createPersistentCookie parameter to false when you call RedirectFromLoginPage(). I could write a much lengthier list of "really dumb coding ideas" to accompany this list of really dumb design ideas, but space does not permit. So let me conclude by stating what should by now be obvious: if you have extensive experience with object-oriented web programming in a multi-tier design paradigm, but simply lack exposure to ASP.NET syntax, you can probably find something useful in this book. Otherwise, stay away!
Rating:
Summary: Worst Technical Book I've Ever Seen
Review: I wanted my money back. I bought this book specifically to prepare me for Exam 70-305. I bought this book because it was the official book from Microsoft so I thought surely this will prepare me for the exam. I found the language in the book stilted and formal. It is written as though English was the second language of the authors. While grammatically, the style is not one that easily conveys ideas. I would have been ok with that though if the book covered the material on the test. This book does not cover remoting at all. Neither does it adequately cover deployment. The only thing the book discusses regarding deployment is xcopy. The official test ask questions about web setup options using installer. I felt really angry about that and felt I had wasted my time and my money. This book will <b>NOT</b> adequately prepare you for the exam.
The test cd that came with the book was next to worthless. The demo questions are not representative in style or content of what they ask on the official test and the demo test is not in a format that is conducive to studying. You dont' know the details of what you missed and why your answers were wrong. If you want a book to get up to speed on .net I highly recommend ASP.NET Unleashed by Stephen Walther. It is a practical book that will be more than adequate for most of the projects you will probably ever work on.
The microsoft test covers more arcane subject matter however so I would not rely on this book either for passing the official test. For the same amount of money you spend on the microsoft book you can go to measureup.com and download or study on line their program for the test. Their test questions are much more representative of the real test in terms of style and content.
The test questions can be analyzed by subject matter and test goal. They reference the sections of either the .net framework documentation or the visual studio .net framework you need to pass the test. I found my study time much more productive in preparing me for the test.
Don't waste your money on the microsoft press book.
Rating:
Summary: I wanted my money back
Review: I wanted my money back. I bought this book specifically to prepare me for Exam 70-305. I bought this book because it was the official book from Microsoft so I thought surely this will prepare me for the exam. I found the language in the book stilted and formal. It is written as though English was the second language of the authors. While grammatically, the style is not one that easily conveys ideas. I would have been ok with that though if the book covered the material on the test. This book does not cover remoting at all. Neither does it adequately cover deployment. The only thing the book discusses regarding deployment is xcopy. The official test ask questions about web setup options using installer. I felt really angry about that and felt I had wasted my time and my money. This book will <b>NOT</b> adequately prepare you for the exam.
The test cd that came with the book was next to worthless. The demo questions are not representative in style or content of what they ask on the official test and the demo test is not in a format that is conducive to studying. You dont' know the details of what you missed and why your answers were wrong. If you want a book to get up to speed on .net I highly recommend ASP.NET Unleashed by Stephen Walther. It is a practical book that will be more than adequate for most of the projects you will probably ever work on.
The microsoft test covers more arcane subject matter however so I would not rely on this book either for passing the official test. For the same amount of money you spend on the microsoft book you can go to measureup.com and download or study on line their program for the test. Their test questions are much more representative of the real test in terms of style and content.
The test questions can be analyzed by subject matter and test goal. They reference the sections of either the .net framework documentation or the visual studio .net framework you need to pass the test. I found my study time much more productive in preparing me for the test.
Don't waste your money on the microsoft press book.
Rating:
Summary: Worst Technical Book I've Ever Seen
Review: I've been in this field for almost 10 years and this is definitely the worst technical book i've ever seen. If the authors were working for me, I'd fire them, quickly. The code is poorly written; doesn't follow C# coding standards published by MS, many of the examples produce errors when compiling the unedited code from the accompanying CD, the text is riddled with wrong information, etc. Do you like debugging code written by authors who are supposed to be showing you how to do things? Much of it doesn't compile. You'll do lots of that. Goto support.microsoft.com and enter knowledge base id = 326884 to see the running list of errors. They gave up compiling the list around page 200 of a 700+ page book (got too long?). Believe me they didn't document more than 10% of the errors in the first 200 pages. Don't waste ANY money or TIME reading this book. There are plenty of other choices.
Rating: 
Summary: Like It
Review: Microsoft has always published great books and this one is also very good. The pace is slow, but it covers a lot of detail. I am looking forward to finishing this book and taking the exam.
| 
