Amazon.com Widgets

Browse by Tags

Framework Design Guidelines: LINQ
Wow, it feels like old times ...  I am happy that we are posting a new proposal for additions to the framework design guidelines.  Mitch has worked hard on these, and we have reviewed them internally and now it is time for your comments.   Read More...
Design Guideline Update: handling nulls in public APIs
We had a recent thread internally that resulted in me updating the guidelines below… Please let me know if you have any questions or comments. Do provide overloads for methods with optional arguments. If a method takes some arguments that are not required Read More...
Design Guideline update: put cleanup code in finally blocks
Another new guideline.. this one sparked a lot of discussion during our internal review, lets see if I cleaned it up well enough or not ;-) Do put cleanup code in finally blocks. Even code that immediately follows a catch() can be interrupted by an asynchronous Read More...
New Design Guideline: Parameter validation
More guideline updates from the Security push (as Soma said earlier this year , the push is now upon us!) Do be aware that mutable values may have changed after they were validated. If the operation is security sensitive you are encouraged to make a copy, Read More...
New Design Guideline: Null Paramarrays
Based on some security reviews we are doing on the system in general I added this implementation note to the Design Guidelines. Do be aware that null could be passed in for the paramarray. You should validate that that paramarray is not null before processing Read More...
New API Design Guideline: Enums
There are a few topics that are likely to generate a long thread of discussion whenever they come up Exceptions, finalization, and Enums are among them Kit George spent a fair amount of time working with folks across WinFX on how to “correctly” Read More...
New Design Guidelines Posted: Resources and Xml
If you have not been tracking Kris’s blog , you might have missed that we recently posted two new design guidelines for Framework developers. As always comments are very welcome, even encouraged. Exposing XML Data Resources Please see the design Read More...
Minor update to Enum size guideline
Here is a minor clarification on the enum size guidelines. Please let me know if you have any questions or comments. As always, you can check out the base design guidelines and my incremental updates. Do use Int32 (the default in most programming languages) Read More...
Design Guidelines Update: Exception Message Guidelines
It has become clear to me recently that we could be doing a better job with exception messages. I took these guidelines from a set that the UE team on the .NET Framework uses. Love to hear your comments, issues, and suggestions. 7.3.2 Exception Error Read More...
Design Guideline Update: Uri vs. string
ChrisAn blogged about this a few weeks ago and I am happy to announce that Krzysztof Cwalina has a guideline ready for you to comment on! System.URI Usage Use System.Uri to represent URI/URL data. This applies to parameter types, property types, and return Read More...
Design Guidelines Update: Enums vs Boolean Arguments
This was a pretty heavily debated guideline internally, I think we reached a good conclusion... Your feedback welcome as always! The full guidelines can be found here , we will be roll this (and other updates) into it for the whidbey release. Enums vs Read More...
Design Guidelines Update: "Core" Method pattern
Minor tweaks to this guideline to line up with what is, I believe, common practice already.. As always questions, comments and annotations to me, and the full guidelines can be found here: http://www.gotdotnet.com/team/libraries ---------- It is recommended Read More...
Pointer Arguments
Somewhat of a niche guideline... but I got questions internally so it seemed worth writting it down and sharing with you. As always, comments welcome -------------------------------------------------- It is very rare but possible to use pointer arguments Read More...
Avoid non-zero based integral indexers for collections
I am clearing out a backlog of Design Guidelines issues... Do use zero based indexes if the collection is integral indexed. Annotation (BradA): In designing the first version of the .NET Framework we went around and around on using zero or one based indexes Read More...
Minor update to the base class guidelines
Fairly minor update -- as always, let me know if there are questions or comments. --------------------------------------------------------- Consider using abstract classes (even if there are no abstract members) if the class is designed to be a root in Read More...
More Posts Next page »

Search

Go

This Blog

Syndication

Page view tracker