لطفا منتظر باشید ...
Why Was This Book Written?
In watching the various message boards and newsgroups around the Internet, it became clear to me that a lot of very smart developers are having some problems making the transition to the object-oriented world of ASP.NET. As much as we praise Microsoft for delivering the platform to us, we can also curse them for making it so inviting and safe because it doesn't force you to follow the "best practices" they envisioned. You can do things in almost the same way you did when you were using a scripting platform.It would be easy to create a straight book on techniques or a "cookbook" of sorts to help you along, but what I'm really after is a guide that helps you understand the underlying concepts and architecture to the platform so that you can apply the same concepts to your own applications. Indeed, I point out in the second chapter that the code you write isn't any different than the code that Microsoft wrote into the thousands of existing .NET base classes. A cookbook or overview wouldn't help you understand this.This book is not meant to evangelize object-oriented techniques. The idea is to show you enough rationale behind the concepts to encourage you to use them. I want light bulbs to go off in your head that say, "Oh yeah, I get it!" Using OOP just for the sake of doing so is not good.
