We have a client/server application which talks via remoting. In our client application we have started migrating to .NET 4.0, at the moment only our plugin's use 4.0, none of the core of the application. This means the application must support
both 4.0 and 2.0. In our app.config for the client we added:
<supportedRuntime version="v4.0" />
<supportedRuntime version="v2.0.50727" />
Our server-side executable is completely built in .NET 2.0 which no references to 4.0. We found when the client passes a dataSet to the server via the remoting connection, it is using System.Data.dll version 18.104.22.168. This is causing an
issue on the server side since there is no .NET 4.0 installed. The question is, why does the client want to use a version 4.0 DataSet when the assembly in the client is built against 2.0 and is there anyway around this behavior?
We can make everything work by installing .NET 4.0 on the server and adding the same startup section above to the server app.config. We need to explain why a customer needs to install .NET 4.0 on ther server when the server application is only referencing
Any help would be greatly appriciates.
View Complete Post