View Single Post
  #3 (permalink)  
Old October 9th, 2003, 05:50 AM
cyber-soft cyber-soft is offline
Registered User
 
Join Date: Oct 2003
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hello, I am get this trouble too. And I found answer on this question in discussion
http://www.thinkdotnet.com/default.a...ic&TopicID=149
This is more complete guide, but a simle instructions include in message of James Wu :
"Starting with .NET Framework v1.1, the remoting infrastructure doesn't automatically deserialize certain types on the server. You must set the server's deserialization level to Full to support automatic deserialization of all types that remoting supports in all situations.

For delegate callbacks working properly, the client's type information or metadata must be present on the server during run-time. Here I just copy the client assembly to the server root directory for convenience. A better solution for that would be creating an EventShim as described in Mike Woodring's sample page(http://staff.develop.com/woodring/dotnet/#RemoteEvents).

Here is the procedure:

Step 1 - Update the channel element in JobClient\JobClient.exe.config to:

channel ref="http" port="0"
serverProviders
formatter ref="binary" typeFilterLevel="Full" /
/serverProviders
clientProviders
formatter ref="binary" /
/clientProviders
/channel

Step 2 - Update the channel element in JobServer\JobServer.exe.config to:

channel ref="http" port="4000"
serverProviders
formatter ref="binary" typeFilterLevel="Full" /
/serverProviders
clientProviders
formatter ref="binary" /
/clientProviders
/channel

Step 3 - Copy JobClient\bin\Debug\JobClient.exe to JobServer\bin\Debug\ "

I am run this f$%@g example from Chapter 3 after changin configuration files and "Step 3". I am ready send my config files for you, if need.

Thank you for attention.

Best regards,

cyber soft