Well, if you don't care about the result and want to take care of the
thread, take a look at Woodring's fire and forget
http://staff.develop.com/woodring/dotnet/#FireAndForget
Regard
Erymuzuan Mustapa
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PR
Perhaps a different approach?
http://nullabletypes.sourceforge.net
I've not used these, but it seems to be something you'll want to look into.
-Original Message-
From: Bill Bassler
Sent: Thursday, October 09, 2003 12:59 PM
When for example retrieving a null value from a database ... bec
I am absolutely bewildered now by the
Microsoft.Samples SSPI and Security assemblies. I've
been trying to set these up in a very straightforward
harness in the way that I'd like to be able to use
them. No IIS. Use TCP, binary. Standard server example
with a console host and console client. .NET 1.1
When for example retrieving a null value from a database ... because the
DateTime structure cannot have null reference assigned to it ...
you end up having to check every time you want to attempt to assign it.
It appears that you can use implicit operator to create wrapper around
DateTime to get a
>> But what's wrong with creating a thread? If you use the
>> threadpool it's almost a one-liner!
>Although if you use the threadpool you almost certainly won't be
>creating a thread - you'll just be using a thread that was already in
>the thread pool most of the time.
>And that's typically a g
