visualbasic month duty inconsistency
i'm operative web concentration controlling vb.net. there also visualbasic formula churned it, sole date non-static month duty vb.
the problem part:
month("10/01/2008")
on servers, i 10 (october) month (which ostensible correct). machine, i 1 (january) (which ostensible wrong).
two colleagues (on possess machines) opposite answers, got 1, got 10.
the doubt is, since so?
on end, i solve problem controlling .net's datetime's parse (or parseexact) duty force all "dd/mm/yyyy" format. works. i'm only wondering since there's an inconsistency.
extra info: i know parameter month duty ostensible date variable. formula used twine parameter, choice despotic off, developers especially let vb the possess reworking thing. (legacy formula maintain lot inertia...)
if helps, chronicle microsoft.visualbasic.dll servers 7.10.6310.4 (under horizon folder v1.1.4322). chronicle cave (and 2 colleagues') accessory 7.10.6001.4.
edit: impromptu settings machines already set dd/mm/yyyy format (short date format).
Comments
Post a Comment