|
From: Jim A. <JA...@th...> - 2004-04-27 17:04:58
|
I remember we had similar problems with DateTimes here (and value types in general) which we fixed. I thought we had sent the patch in for inclusion, but I'll double check that and get back to you. Jim ThoughtWorks |---------+-----------------------------------------> | | "Nick Robinson" | | | <nicholasrobinson@fromconcept.| | | co.uk> | | | Sent by: | | | nmo...@li...| | | ceforge.net | | | | | | | | | 26/04/2004 15:24 | | | | |---------+-----------------------------------------> >------------------------------------------------------------------------------------------------------------------------------| | | | To: nmo...@li... | | cc: | | Subject: [Nmock-general] Dates | >------------------------------------------------------------------------------------------------------------------------------| I have a colleague who has tried to Mock a DateTime field on an interface: IFoo { DateTime Date { get; set; } } When a mock of IFoo is passed into a client call, access of non-DateTime properties work, but an access to the Date property generates an error about the object reference being null. Is there a known issue with Dates? Nick. ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ Nmock-general mailing list Nmo...@li... https://lists.sourceforge.net/lists/listinfo/nmock-general |