On Fri, 22 Aug 2003, J. Merrill wrote:
> See the section titled "Passing Data to Threads" in the "Creating
> Threads" document in the .NET Framework docn; you can get to it by
> finding "creating" under "threads" on the left side of the help
> window.
The problem is not to pass *any* data to a th
I'm trying to find an answer to a seemingly straightforward question,
but it is proving more difficult than I thought it would.
The question is: if I create an array of pointers, using unsafe code in
C#, will the elements of the array all be initialized to null?
The documentation in the C# spec i
Thanks Wenfeng!!
I hope I can use this to implement some security feature and shouldn't
be a security threat to the application if the code logic is fine.
Thanks anyway,
Sujay
-Original Message-
From: Wenfeng Gao [mailto:[EMAIL PROTECTED]
Sent: Friday, August 22, 2003 9:51 PM
To: [EMAI
Yes, Brant's statement is incorrect.
If you want the full exception serialised to the client you should put
the customErrors tag in the server .config file where I said and you
should get the exception properly. This change was due to the
tightening up of security for remoting, similar to the typ
Chris Day -- did you mean "is incorrect" when you say "is...WRONG!"? That is, did you
mean that Brant Fallin's statement -- that "the customError [sic -- typo for
customErrors] element is ignored by remoting architecture at the moment" -- is not
correct?
The docn seems to agree that is what y
