"Grant Schenck" <schenckg@optonline.net> wrote in message
news:uZyG6Q$9HHA.3548@TK2MSFTNGP06.phx.gbl...
> I'm trying to mark my methods as OneWay but the compiler won't accept it.
> I keep getting "The type or namespace 'OneWay' could not be found (are you
> missing a using director or an assembly reference?)"
>
> Any idea how I can mark a remote method as one way???
>
>

"Doug Semler" <dougsemler@gmail.com> wrote in message
news:eDdRUYB%23HHA.4180@TK2MSFTNGP05.phx.gbl...
> "Grant Schenck" <schenckg@optonline.net> wrote in message
> news:uZyG6Q$9HHA.3548@TK2MSFTNGP06.phx.gbl...
>> I'm trying to mark my methods as OneWay but the compiler won't accept it.
>> I keep getting "The type or namespace 'OneWay' could not be found (are
>> you missing a using director or an assembly reference?)"
>>
>> Any idea how I can mark a remote method as one way???
>>
>>
>
>
> using System.Runtime.Remoting.Messaging;
>
> Be careful, though, the client making the call cannot make ANY assumptions
> about whether the server accepted and/or ran the call that you are making
> to completion.
>
> In other words, it is only useful in a "I want to call this but don't care
> if it succeeds or not" scenario.
>
> --
> Doug Semler, MCPD
> a.a. #705, BAAWA. EAC Guardian of the Horn of the IPU (pbuhh).
> The answer is 42; DNRC o-
> Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
> erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?
>

"Grant Schenck" <schenckg@optonline.net> wrote in message
news:%23NicEwF%23HHA.464@TK2MSFTNGP02.phx.gbl...
> Thanks!
>
> That did the trick. I can't tell you how long I searched MSDN + Google to
> try to find what I needed for oneway...

"Doug Semler" <dougsemler@gmail.com> wrote in message
news:e38ORnH%23HHA.5840@TK2MSFTNGP03.phx.gbl...
> "Grant Schenck" <schenckg@optonline.net> wrote in message
> news:%23NicEwF%23HHA.464@TK2MSFTNGP02.phx.gbl...
>> Thanks!
>>
>> That did the trick. I can't tell you how long I searched MSDN + Google
>> to try to find what I needed for oneway...
>
> It's in MSDN but sometimes it takes a fresh set of eyes. You probably
> forgot that in MSDN, an attribute is actually docuemented as
> "OneWayAttribute" <g> Once you get to that point, you see the namespace
> and assembly it resides in.
>
> --
> Doug Semler, MCPD
> a.a. #705, BAAWA. EAC Guardian of the Horn of the IPU (pbuhh).
> The answer is 42; DNRC o-
> Gur Hfrarg unf orpbzr fb shyy bs penc gurfr qnlf, abbar rira
> erpbtavmrf fvzcyr guvatf yvxr ebg13 nalzber. Fnq, vfa'g vg?