ActiveSocket Network Communication Toolkit by ActiveXperts Software - HTTP, HTTPs, FTP, ICMP, SNMP Get/GetNext/Set, SNMP Traps, NTP, RSH, Telnet and more
Visit ActiveSocket Web Site
Download ActiveSocket Network Communication Toolkit
Book: "Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries"
||Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries
||Krzysztof Cwalina, Brad Abrams
|Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries teaches developers the best practices for designing system frameworks and reusable libraries for use with the Microsoft .NET Framework and WinFX. This book focuses on the design issues that directly affect the programmability of a framework, specifically its publicly accessible APIs.
This book can improve the work of any .NET developer producing code that other developers will use. An added benefit is a collection of annotations to the guidelines by various members of the Microsoft .NET Framework and WinFX teams, which provide a lively discussion of the motives behind the guidelines, along with examples of good reasons for breaking the guidelines.
Microsoft architects Krzysztof Cwalina and Brad Abrams offer guidelines for framework design from the top down. From their long experience and deep insight, you will learn:
- The general philosophy of framework design
- Principles and guidelines that are fundamental to overall framework design
- Naming guidelines for the various parts of a framework, such as namespaces, types, and members
- Guidelines for the design of types and members of types
- Issues and guidelines that are important to ensure appropriate extensibilityin your framework
- Guidelines for working with exceptions, the preferred error reporting mechanism in the .NET Framework and WinFX
- Guidelines for extending and using types that commonly appear in frameworks
- Guidelines for and examples of common framework design patterns
Guidelines in this book come in four major forms: Do, Consider, Avoid, and Do not. In general, a Do guideline should almost always be followed, a Consider guideline should generally be followed, an Avoid guideline indicates that something is generally not a good idea, and a Do not guideline indicates something you should almost never do. Every guideline includes a discussion of its applicability, and most guidelines include a code example.
A companion DVD includes the Designing .NET Class Libraries video series, instructional presentations by the authors on design guidelines for developing classes and components that extend the .NET Framework. A sample API specification and other useful resources are also included.