///
public object CodePage;
Why don't they just define it as an int and define some value or exception indicating, that CodePage is not set?
Donnerstag, 17. Januar 2008
Visual Studio 2008 SDK Goodies #2
In ProjectOptions.cs in the Managed Package Framework of Visual Studio 2008 SDK you'll find funny field definitions, e.g.:
///must be an int if not null
public object CodePage;
Why don't they just define it as an int and define some value or exception indicating, that CodePage is not set?
///
public object CodePage;
Why don't they just define it as an int and define some value or exception indicating, that CodePage is not set?
Abonnieren
Kommentare zum Post (Atom)
Posts
Keine Kommentare:
Kommentar veröffentlichen