Hi,
bclubb, I read the article and it's not really my problem. So I continued to search and finally found something.
Let's me explain my problem. I've a client/server application, and the communication between the client and the server is based on remoting (TCP / Binary).
On the client i need to show invoices in a datagrid, so the client call a service on the server by remoting.
On the server i use an adapter (with SqlServer) to fetch a TypedList, and return it to the client.
On the client i set the datasource of my datagrid with the typedlist.
Invoices have a SendDate which can be null in the database. In the datagrid when the SendDate is null the value "01/01/01 01:01" appears in the cells.
That's not normal ! I've to see a blank cell.
I think the problem is due to the serialization of the TypedList. Because if i fetch the typedlist on the client side (only a test, because client can't access the database in the real life
) blank cells appears for null values.
So, i make an other test in two parts.
First part, in a simple application, i fetch a typed list. Bind it to a datagrid, all is correct with nullable date.
Second part, i fetch the same typed list, serialize it with a BinaryFormatter. Deserialize the typed list and bind to the datagrid : "01/01/01 01:01" appears for null dates !
I'm using VB.Net 2.0 and LLBLGen V2. With LLBLGen V1 I didn't have the problem... Did you change something between V1 and V2 in the typedlist serialization ?