Who Should Read This Book?Codersthose who are banging out the code, day in and day out. There are some portions of this book, mainly Chapters 1 and 2, that can be useful for managers who are wondering how Open Source licensing could affect their proprietary product. But for the most part, this book assumes a fair amount of C# and .NET knowledge. It is not a book on how to learn the .NET platform or necessarily how to set up the different .NET environments. Rather, this book shows how to use the many different projects and products together. To me, it all comes down to getting the job done and using the right tool for the job. Sometimes that tool, component, or framework might be Open Source; sometimes it is not. This book will help you understand how to evaluate the tool that best fits your needs.Have you ever felt like you just kept doing similar coding tasks over and over again on different projects? This is initially a fun, "I know exactly how to do this!" sort of a thing. But then it turns into something unexciting and mundane, like the difference between the excitement of the very first business trip you ever took and the last one you endured for the sake of your company. At first creating something as basic as a logging mechanism sounds fun and easy, but when you are done and show it to the people who will use it, you quickly find out the inadequacies: "It's too hard to use," "This doesn't support enough," or "It isn't extendable!" Many of the projects in this book address just this problem. These frameworks and components have seen a lot of runtime and have nice APIs from the many developers who use them. However, keep in mind that the greatest feature of Open Source is that the Source is Open! Not that it saves you time in not having to implement some feature, or that it is cheaper, faster, or more secure than its closed source counterparts, but that you can gain a relatively large amount of experience in a small amount of time by looking at many different code bases and designs. |
لطفا منتظر باشید ...
