Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Windows Forms / Design Time / January 2005

Tip: Looking for answers? Try searching our database.

Visual Deisnger Bug with Long values?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
cody - 28 Jan 2005 12:26 GMT
I have a component an IntegerTextBox in which the user can use large
numbers. The defaultvalue of the "long MaxValue{get;set;}" property is
long.MaxValue.

The problem now is that the designer generates the number in the code in the
following format:

this.tbBelegNummer.MaxValue = ((long)(9223372036854775807));

Now if I open the Form in the designer the value is mistakenly parsed as -1
and I get an ArgumentOutOfRangeException thrown by may component because I
have set MinValue to 0.

Is this a known bug with deserializing long numbers with the designer?
joeycalisay - 31 Jan 2005 06:55 GMT
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?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.