tag:blogger.com,1999:blog-41537452104625210432011-07-28T19:44:39.289-07:00Ra-elhttp://www.blogger.com/profile/05313489480820171542noreply@blogger.comBlogger21100tag:blogger.com,1999:blog-4153745210462521043.post-19969553421903132352010-08-12T17:18:00.000-07:002010-08-18T01:26:51.508-07:00

I'm sure you've come accross the feeling that although they are handy at first enums have limitations when it comes to OOP. Here is an implementation that gives you the goodness of enums, having a set of named items that identify things, and adds encapsulation of functionality which I've always felt enums lack. Lets start off with a simple implementation that represents a time interval (

Ra-elhttp://www.blogger.com/profile/05313489480820171542noreply@blogger.com2tag:blogger.com,1999:blog-4153745210462521043.post-68096809822736141942010-08-11T00:55:00.000-07:002010-08-11T01:22:07.237-07:00

I am currently working on some code that I'm hoping will become a tool that is able to view the output of .Net's BinarySerializer.First a bit of background. I use Windows Workflow Foundation (WF) at my work and serialize its state to the database. As time has gone on and we have had different versions of the workflows and the objects they depend upon we have sometimes had problems deserializing

Ra-elhttp://www.blogger.com/profile/05313489480820171542noreply@blogger.com0