Hi,

I wanted to use LLBLGen with the Compact Framework .NET 2.0. One of the things I wanted to do was save a custom class as an Integer field in the database. However I read in the Help that Type Converters are not supported for the Compact Framework. Is this really true? Is there some other feature in LLBLGen that lets me do this?

Will Type converters be supported in a future version of LLBLGen? And if so, when can we expect it?

Thanks for your reply.

Robert

One of the things I wanted to do was save a custom class as an Integer field in the database.

So you want to have an instance of this custom class as an EntityField inside an entity. If so then you are right you will need a TypeConverter.

But unfortunatly TypeConverters aren't supported on the CF, since they inherit from System.ComponentModel.TypeConverter which is not supported on the CF.

So as long as System.ComponentModel.TypeConverter isn't supported on the compact framework, this feature isn't supported too.

Walaa wrote:

One of the things I wanted to do was save a custom class as an Integer field in the database.

So you want to have an instance of this custom class as an EntityField inside an entity. If so then you are right you will need a TypeConverter.

But unfortunatly TypeConverters aren't supported on the CF, since they inherit from System.ComponentModel.TypeConverter which is not supported on the CF.

So as long as System.ComponentModel.TypeConverter isn't supported on the compact framework, this feature isn't supported too.

Not the answer I was hoping for, but at least it's clear I don't have to try to use LLBLGen. Thanks.

BTW I checked and the Compact Framework does "support" TypeConverter, but no real methods on it. I sometimes don't understand the decisions they made leaving such functionality out of the CF.

Yes, tell me about it... 'SortedList'.. not supported... assembly / appdomain methods.. nope... etc.

The thing with typeconverter is that we wanted a way to define a type converter once and make it usable in the designer AND the runtime, but at the same time avoid having to reference an assembly for typeconverters both in the designer and the runtime (which would tie the runtime to the designer and vice versa.)

The .NET Typeconverter class was ideal for this. But unfortunately, this is indeed a problem on compact framework.