By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,934 Members | 1,692 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,934 IT Pros & Developers. It's quick & easy.

Why configure Soap formatter for HTTP Binary Remoting - .NET Framework 1.1

P: n/a
Hello All,

Recently I had posted a message to forum requesting assistance to resolve a
security issueI was facing in .NET Framework 1.1, the error being "Because
of Security Restrictions, the ObjRef cannot be accessed". The solution was
in the server's app.config file where I had to set the 'typeFilterLevel' to
'Full' for both the SOAP as well as the Binary formatters. My remoting
environment was set for Server activated components (so no config file or
configuration in the client side) and I used TCP / Binary for communication.
Initially I just configured the app.config to reflect the Binary formatter
as follows:

<serverProviders>
<formatter ref="binary" typeFilterLevel="Full"/>
</serverProviders>

This I added to the channel element in the app.config and it did not resolve
the issue, I was still getting the same errors. I tried to read through but
could not find any specific article explaining why it still happened. I
tried configuring both the SOAP and Binary formatters and it worked.

My question is why do I have to set the 'Soap' formatter's 'typeFilterLevel'
to 'Full' to get TCP Binary to automatically deserialize.

Any theories would be of great help.

regards,
Chris
Jul 19 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.