Commonality - TypeConverter, Arrays and ASP.NET

Fri, 25 Jul 2008 18:13:54 GMT

This should've been simple, but it took me a far longer time than I expected to get working correctly. Getting the basic design time work done wasn't too much of a problem; since the property type was an array and not a custom collection, the default editors did the right thing and offered a good design time experience out of the box. However, you still need to provide the designers and ASP.NET a way to store the property contents as an string, so that you can use markup to specify the value of the property. Time to write a TypeConverter! I went ahead and wrote a simple TypeConverter that would take a string and return an array of structs based on its contents, or take an array and return a string based on the values in it. Nothing fancy.

Choosing Between Classes and Structs

Sat, 12 Jan 2008 17:00:28 GMT

A little dry, but gets the basic concept about when to choose a structure over a class, and vice versa.

DotNetKicks.com - Stories tagged with Struct

Commonality - TypeConverter, Arrays and ASP.NET

Choosing Between Classes and Structs