![]() | |
![]() |
| | Thread Tools | Search this Thread | Display Modes |
#11
| |||
| |||
|
|
BinarySerialization (Level?) = Full on both the client AND server level serialization methods. This gets around type serialization issues. IPC communications in .NET 2 gives default access. On XP+ that means that CREATOR OWNER is the only one that is gonna be able to write to it. you can get around this by either specifying an authenticationLevel attribute name (i believe that's the name it may be slightly different....MSDN has the right one) to the user group of the IPC access. Or, if you are creating the IPC server/client by "hand" you should be able to specify the acces group. Remember, an IPC connection type is implemented as a named pipe, which means it follows the same DACL rules of named pipes. -- 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? |
#12
| |||
| |||
|
#13
| |||
| |||
|
|
Yeah I know. We actually redesigned our solution at one point to specficially avoid remoted events. Ingo Rammer's book has a good demonstration on how to do remoted events if you haven't already looked into that. Sorry, I would help you more but I had four teeth pulled today and am a bit out of it. If I htink of anything else over the weekend i'll post. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |