This week I had a hard day to track down a remoting issue we had with our product. Basically, we have remote cache server, that uses .NET remoting to store binary serialized information, which is shared across all our apps, and projects.
In our task of finding an optimal migration path so that we could put all new development in 2.0 while still keep all the 1.1 apps alive, we stumbled into this horrendous problem.
Basically, in .NET 2.0, there are some changes to some of the native types, the two biggest culprits are Dataset, and Date Time. Dataset is workable, and you can work around easy enough, date time is much more complicated, because you fall into an issue of having date time objects embedded in other objects, data tables, datasets, custom objects and more. Trying to find all the date times, to handle them would be near impossible, and also a major performance hit, which would be unacceptable.
I still have no solution for this problem, supposedly there will be a patch for the 1.1 framework for this issue, however I can't find this patch yet.
All in all, Microsoft did a fantastic job of having 2.0 support and upgrade 1.1 apps with almost no issues. It took this complicated setup to stumble upon discovery of this issues ( which I found a whole of 3 relevant forum discussions on, and still no useful solution ).
Anyway, if you have large setups where you have 1.1 removing, keep in mind, you are likely to find some issues having that app and your 2.0 app talk to each other if serialization is used.
Oh well, I hope I can find this patch quick... if not... I just do not know how I will work around this.
******** UPDATE ********
I have found out today, thanks to the great help from a few dedicated Microsoft employees, that there is a patch being released, hoepfully in the next month or so, however if you have product support services account, you can get it now, when it is released it will be KB 907262. Many thanks to the guy's who took their time to help me out.