Comments on: Late Binding of C# objects from NHibernate into the ASP.NET DataGrid control http://blog.headlondon.com/2006/04/26/late-binding-of-c-objects-from-nhibernate-into-the-aspnet-datagrid-control/ Digital design agency, creative content, brand identity, web development, online marketing, application creation, integrated Wed, 29 Jun 2011 13:47:31 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Dave Hrycyszyn http://blog.headlondon.com/2006/04/26/late-binding-of-c-objects-from-nhibernate-into-the-aspnet-datagrid-control/comment-page-1/#comment-32 Dave Hrycyszyn Wed, 26 Apr 2006 14:17:40 +0000 http://blog.headlondon.com/archives/late-binding-of-c-objects-from-nhibernate-into-the-aspnet-datagrid-control/#comment-32 Just as a note: thinking about it some more, I really prefer this way of doing late binding to the loose-typing VB.NET way. The reason is pretty simple - there is absolutely no way to screw it up, due to type safety. In VB.NET, you could just say something like: Option Strict Off ...and then proceed to access any property or method of the Article object (which is in fact just an object). The trouble would be that if you blew it and forgot to implement, let's say, Title in one of your classes, you'd get a runtime error when a user tried to access your code. Using the IContent interface ensures that any class that implements IContent *must* have a Title, Id, etc. So, even in VB.NET, this technique of casting to an interface is still the way to go. Just as a note: thinking about it some more, I really prefer this way of doing late binding to the loose-typing VB.NET way. The reason is pretty simple – there is absolutely no way to screw it up, due to type safety. In VB.NET, you could just say something like:

Option Strict Off

…and then proceed to access any property or method of the Article object (which is in fact just an object). The trouble would be that if you blew it and forgot to implement, let’s say, Title in one of your classes, you’d get a runtime error when a user tried to access your code. Using the IContent interface ensures that any class that implements IContent *must* have a Title, Id, etc. So, even in VB.NET, this technique of casting to an interface is still the way to go.

]]>