Whidbey Remoting AccessViolation Problem [Maheshwar Jayaraman]

There has been some cases where users have reported an AccessViolation when upgrading their Remoting app’s to Whidbey. Some users found that the problem repro’d only when they had some anti virus software (Nod32 in particular) installed and the AV went away when they configured the anti-virus not to scan the problematic exe’s. We managed to…

1

Remoting Performance and Auto Web Proxy [Hoop Somuah]

The .Net Framework 2.0 has significant changes to its support for proxies including support for connection-specific proxy settings, automatic proxy configuration and the ability to automatically refreshing proxy settings whenever the active connection changes. These features can be very useful in .Net Remoting but the auto web proxy feature can also affect performance. If you…

2

Channel Properties [Sowmy Srinivasan]

As Doug indicated I was going to post my deranged .NET Remoting ramblings in my blog. But then John had created this cool blog especially for our Remoting users. So I’ll start putting my Remoting posts here.   One of the most frequent problems users run into is the lack of strong types to set channel properties. Today the user has…


Uniquely identifying clients using CallContext [Gagan Gupta]

Here is a remoting sample that demonstrates a way to communicate IP address from client to service (it can be easily tweaked to do vice-versa). Sample uses CallContext [1] to achieve this communication. CallContext provides ability to pass data from one call to another and “flow” the data in the background as opposed to explicitly…

1

Configuring Kerberos Delegation with .NET Remoting 2.0 [Rick Rainey]

Version 2.0 of the .NET Framework supports the use of ‘secure channels’.  These are powerful new features but they can be extremely challenging to setup. For example, I recently was tasked with trying to get an application to use Kerberos delegation in a double hop scenario and found that while my application was actually working,…

3

SerializationException with IIS [Utkarsh Shah]

If you are getting an error stating that…System.Runtime.Serialization.SerializationException was unhandled  Message=”The input stream is not a valid binary format. The starting contents (in bytes) are: 53-65-72-76-65-72-20-65-6E-63-6F-75-6E-74-65-72-65 …” This typically happens when IIS sends back an error message as plain text which the binary formatter doesn’t know how to handle. Try changing the formatter to SoapFormatter;…


TCP Eventing [Utkarsh Shah]

Eventing is reliable in case of named pipe scenarios on same machine but not over network. So if underlying sockets close connection eventing won’t try to establish it for you. Using events over network is not recommended. But if you still want to use it, this post takes us over a simple client server example…

1