The .NET Framework's managed environment allows developers to improve their programming model to support a wide range of functionality. The goal of the .NET Framework design guidelines is to encourage consistency and predictability in public APIs while enabling Web and cross-language integration. It is strongly recommended that you follow these design guidelines when developing classes and components that extend the .NET Framework. Inconsistent design adversely affects developer productivity. Development tools and add-ins can turn some of these guidelines into de facto prescriptive rules, and reduce the value of nonconforming components. Nonconforming components will function, but not to their full potential.
These guidelines are intended to help class library designers understand the trade-offs between different solutions. There might be situations where good library design requires that you violate these design guidelines. Such cases should be rare, and it is important that you provide a solid justification for your decision. The section provides naming and usage guidelines for types in the .NET Framework as well as guidelines for implementing common design patterns.
Read more: I have delicious Design Guidelines for Class Library Developers.
3 weeks ago
1 comment:
Hello Imranbhai,
Thanks for maintaining such a Informative blog. I had got very little time to work with you, but I had enjoyed ur way of programming, no matter wht things goes between us... but I had learn few things from that little time, which I think only true programmer can able to taught anyone... Thanks for tht.
Keep Going Good Work.
Post a Comment