There’s No Substitute For The Real (.NET) Thing
Sometimes, the .NET framework’s backwards compatibility doesn’t work, and you have to install the exact version required by an assembly.
Recently, I was working on a project that used a number of components compiled for .NET 1.1 (I didn’t have the source code) — and, since I strongly prefer Visual Studio 2005 over the earlier versions, I was writing my test code in VS 2005, which installed .NET 2.0 only on the computer.
The result?Â No obvious error messages from .NET (which I would’ve expected if there were version incompatibilities), but the .NET Remoting portion did not work.Â The only error message was about being unable to serialize an object.
The solution?Â I installed the .NET framework V1.1, and the Remoting (and serialization) problems went away.