This can be helpful:
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.windowsfor
ms.designtime/browse_thread/thread/86aacc13d1605f3b/ce4b7d72608c841b?q=deseriali
ze+property+number&_done=%2Fgroup%2Fmicrosoft.public.dotnet.framework.windowsfor
ms.designtime%2Fsearch%3Fgroup%3Dmicrosoft.public.dotnet.framework.windowsforms.
designtime%26q%3Ddeserialize+property+number%26qt_g%3D1%26&_doneTitle=Back+to+Se
arch&&d#ce4b7d72608c841b

Signature
Joey Calisay
http://spaces.msn.com/members/joeycalisay/
> I have a component an IntegerTextBox in which the user can use large
> numbers. The defaultvalue of the "long MaxValue{get;set;}" property is
[quoted text clipped - 10 lines]
>
> Is this a known bug with deserializing long numbers with the designer?
cody - 31 Jan 2005 12:26 GMT
Thank you there seem to be a lot of similar bugs like this in the visual
designer.
I helped myself now in that I assign the properties in code and not in the
designer and put a designerserialisationvisibility hidden attribute on the
property.
> This can be helpful:
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.window
sforms.designtime/browse_thread/thread/86aacc13d1605f3b/ce4b7d72608c841b?q=d
eserialize+property+number&_done=%2Fgroup%2Fmicrosoft.public.dotnet.framewor
k.windowsforms.designtime%2Fsearch%3Fgroup%3Dmicrosoft.public.dotnet.framewo
rk.windowsforms.designtime%26q%3Ddeserialize+property+number%26qt_g%3D1%26&_
doneTitle=Back+to+Search&&d#ce4b7d72608c841b
> --
> Joey Calisay
[quoted text clipped - 16 lines]
> >
> > Is this a known bug with deserializing long numbers with the designer?