.net framework Version can create conflict in WCF Service and client?

Question

4.00/5 (1 vote)

See more:

.NET3.5

I had developed a WCF Service in .net framework 4.0 and Client in .net framework 3.5. Does it create a problem? I mean it is possible to for .net framework 3.5 can consume the service which is build on .net framework 4.0 and using binding "wsDualHttpBinding"? I had tested in the two situation where one service is created by using .net framework 3.5 and another one is created by using .net framework 4.0. when I try to connect service which was created by using .net framework 3.5 and which is hosted in IIS then it get connected. And another one when I try to connect service which was created by using .net framework 4.0 and which is hosted in IIS then it get unconnected. this is tested in Localhost. any suggestion?

Thank you in advance.

Posted 22-Jan-14 22:24pm

Akashkumar Bammrotwar

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sampath Lokuge · Answer 1 · 2014-01-22T23:06:00

No,Always you can do this.B'cos it's having backward compatibility with the earlier version.
So, if you're having something wrong,it should give the same error on your local host also.Hence, you don't have any problem with local host means where may be the problem with something else.So try to find that thing by using log information of your service.