Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Class design or rather redesign
Message
De
17/03/2005 11:12:46
Cetin Basoz
Engineerica Inc.
Izmir, Turquie
 
Information générale
Forum:
ASP.NET
Catégorie:
Autre
Divers
Thread ID:
00996809
Message ID:
00996849
Vues:
9
>Sorry about the vague title.
>
>Here is the story I have this simple little class (just a few properties and methods), now a new requirement has come along (as they usually do) that requires me to add a new property to the class. The only problem with this property is that it can only be populated if the app is running in conjunction with (learned that from the VFP EULA <s>) Win Xp or above.
>So my initial thought was to add 2 new properties one for the new property and one to state if the 1st property can/should be used or not.
>Or should I design the new property so that the user of the class has to read my notes and know to check if OS version is XP or higher before trying to get the property.
>
>Any thoughts related to this would be greatly appreciated.
>
>Einar

Einar,
Woudln't it be something like:

{set {if (winXPorLater) _myField = value; }}

Cetin
Çetin Basöz

The way to Go
Flutter - For mobile, web and desktop.
World's most advanced open source relational database.
.Net for foxheads - Blog (main)
FoxSharp - Blog (mirror)
Welcome to FoxyClasses

LinqPad - C#,VB,F#,SQL,eSQL ... scratchpad
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform