Current Date Time

[Jim Heavey]

2 questions...

The documentation shows a "property" call Now, which returns the current
date and time, but it is not valid for how I am using it.

If you declare a field as a DateTime, but never populate it, how can you
tell if it is null?

[William Ryan]

Jim:

What do you need to do with it? For instance, DateTime.Now has a lot of
formatters and can do just most anything I've ever come across.

I don't have my IDE in front of me, but if you don't assign the object a
value, it should be null in C# or nothing in VB.NET. If may have some
other value, but I would think it'd be null. You can declare a DateTime in
the IDE and breakpoint before it. Step past it and see what it's value is.
You can check for whatever that is afterward.

HTH,

Bill
"Jim Heavey" <Ji*******@nosp am.com> wrote in message
news:Xn******** *************** **********@207. 46.248.16...

2 questions...

The documentation shows a "property" call Now, which returns the current
date and time, but it is not valid for how I am using it.

If you declare a field as a DateTime, but never populate it, how can you
tell if it is null?

[William Ryan]

Jim:

I just remembered something...Dat eTime is a value type, nix that last
suggestion. Let me play with it for a second and I'll post back.
"Jim Heavey" <Ji*******@nosp am.com> wrote in message
news:Xn******** *************** **********@207. 46.248.16...

2 questions...

The documentation shows a "property" call Now, which returns the current
date and time, but it is not valid for how I am using it.

If you declare a field as a DateTime, but never populate it, how can you
tell if it is null?

[JR]

Hi,

DateTime DoStuff()
{
DateTime dateTime = DateTime.MinVal ue;

// Do other stuff.

return(dateTime );
}

void DoMoreStuff()
{
DateTime dateTime = DoStuff();

if(dateTime == DateTime.MinVal ue)
{
// invalid date.
}
}

John.

"Jim Heavey" <Ji*******@nosp am.com> wrote in message
news:Xn******** *************** **********@207. 46.248.16...

2 questions...

The documentation shows a "property" call Now, which returns the current
date and time, but it is not valid for how I am using it.

If you declare a field as a DateTime, but never populate it, how can you
tell if it is null?

[David]

On 2004-01-03, Jim Heavey <Ji*******@nosp am.com> wrote:

2 questions...

The documentation shows a "property" call Now, which returns the current
date and time, but it is not valid for how I am using it.

If you declare a field as a DateTime, but never populate it, how can you
tell if it is null?

DateTime object are value types, they are never null, in the same way
that ints and longs can never be null.

If you declare a local variable as DateTime, the compiler won't let you
use it until you populate it. If you declare a member variable as a
DateTime, it will be equal to DateTime.MinVal ue.

And I'm not really sure what your first question refers to. How do you
want to use it?
--
David
dfoster at
hotpop dot com

[Jay B. Harlow [MVP - Outlook]]

Jim,
In addition to the others comments about using DateTime.MinVal ue.

You might consider using System.Data.Sql Types.SqlDateTi me, as it is a value
type that has the concept of being "Nullable".

Hope this helps
Jay

"Jim Heavey" <Ji*******@nosp am.com> wrote in message
news:Xn******** *************** **********@207. 46.248.16...

2 questions...

The documentation shows a "property" call Now, which returns the current
date and time, but it is not valid for how I am using it.

If you declare a field as a DateTime, but never populate it, how can you
tell if it is null?