Prev: More about application domain
Next: When to use one application domain instead of several
From: bill tie on 17 May 2010 07:41
In Vs2k10, when I write

IAsyncResult result = myFunkyDelegate.BeginInvoke(arg1, arg2, ...)

Intellisense offers named arguments, e.g. "callback:", in which case I write
callback: new AsyncCallback(myMethod).

For the argument that is passed to the callback method, Intellisense offers
"object:". If I accept the offered name, and write object: myFunkyDelegate,
the compiler doesn't like it, probably because the name "object" conflicts
with the C# keyword.

How should a situation like this be dealt with?

From: Jeff Johnson on 17 May 2010 09:38
"bill tie" <billtie(a)discussions.microsoft.com> wrote in message
news:E11724C9-2D6F-4396-8183-0741703C0BBC(a)microsoft.com...

> In Vs2k10, when I write
>
> IAsyncResult result = myFunkyDelegate.BeginInvoke(arg1, arg2, ...)
>
> Intellisense offers named arguments, e.g. "callback:", in which case I
> write
> callback: new AsyncCallback(myMethod).
>
> For the argument that is passed to the callback method, Intellisense
> offers
> "object:". If I accept the offered name, and write object:
> myFunkyDelegate,
> the compiler doesn't like it, probably because the name "object" conflicts
> with the C# keyword.
>
> How should a situation like this be dealt with?

....don't use the named argument syntax?


 | 
Pages: 1
Prev: More about application domain
Next: When to use one application domain instead of several