Framework Design Guidelines: System.DBNull

Posted by: Brad Abrams, on 10 Feb 2009 | View original | Bookmarked: 0 time(s)

Continuing in our weekly blog post series that highlights a few of the new additions to the Framework Design Guidelines 2nd edition.. This content is found in the Nullable<T> section of Chapter 8: Usage Guidelines. Pablo helps us out with some subtle details that might really come in handy. AVOID using System.DBNull. Prefer Nullable<T> instead. PABLO CASTRO Nullable<T> is in general a better representation of optional database values. One thing to consider though is that...

Category: .NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 969 | Hits: 45

Similar Posts

  • My History of Visual Studio (Part 7) more
  • Belgium Visual Studio Users Group: 10 Years of Framework Design Guidelines more
  • Working on Silverlight .NET RIA Services Part 2 more
  • Open SQL Port for specific IP by ASP.NET Website more
  • EF4 New Properties for Entity Properties? more
  • Update to Logging in to DotNetNuke from a Silverlight Application with RIA Authentication more
  • SQL 2008 CLR Triggers, use a .NET class library in SQL using WPF more
  • Logging in to DotNetNuke from a Silverlight Application with RIA Authentication more
  • WSE, DIME; WCF, MTOM; OH My! more
  • Server vs. Client Empowered Web Applications more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD