Problem with WCF service reference updation

Question

5.00/5 (1 vote)

See more:

Hi All,

I am stuck in a very strange problem. I am consuming a wcf service in asp.net project using VS2010. Everything was fine before, but suddenly wcf service updation started behaving strangly. As soon as i update the service reference by right clicking on the service and selecting Update Service Reference, it deletes all the end points from web.config and clears the Referece.cs file. But it doesn't rewrite anything in both files. That means its not updating properly. Even delete and add of service reference dint work.

But the same reference works fine when i add it into any other project. Looking forward any guidance to solve this problem.

Thanks in advance

Posted 16-May-11 23:26pm

Vicky2Galaxy

Add a Solution

2 solutions

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)

Vicky2Galaxy · Answer 1 · 2011-05-22T20:33:00

Solution 2

Hi... Finally i have found the reason behind this issue...it's because of some common assemblies referred in WCF service project and Consuming project. I removed those assemblies from consuming project and everything started working fine... :)
Thanks Wannes for your help ....

Posted 22-May-11 20:33pm

Vicky2Galaxy

Wannes Geysen · Answer 2 · 2011-05-16T23:39:00

Solution 1

I had the same problem once with my WCF Service. The problem occurs when I used unknown types to transfer between the service and the client.

try the microsoft test client to connect to your service and maybe this tool will give you some clue to which method is wrong. more info: see http://msdn.microsoft.com/en-us/library/bb552364.aspx[^]

Otherwise you can also comment all the Operationcontracts one by one and try to update your service reference each time. So you can discover which is the incorrect OperationContract

Posted 16-May-11 23:39pm

Wannes Geysen

Comments

Vicky2Galaxy 17-May-11 6:13am

Hi wannes.. thanks for the reply.. i tried the tool but couldn't figure out the problem.. infact service should behave similar in all consuming projects if this is the reason. But its creating problem only in one project...

Wannes Geysen 17-May-11 6:16am

And you didn't change something at the service contract recently?
If I understand correct: if you update the service reference at another client project, there is no problem?

Vicky2Galaxy 17-May-11 6:20am

yes .. you are right.. :)

Wannes Geysen 17-May-11 6:24am

strange :)

Wannes Geysen 17-May-11 6:28am

Can you post your service interface class here with the servicecontract?

Vicky2Galaxy 17-May-11 8:53am

Is this something to with a kind of client side (referrer) configuration changes i.e very specific to the client project?

Wannes Geysen 17-May-11 9:15am

I don't understand what you mean. Can you explain a little bit more?

Vicky2Galaxy 18-May-11 5:56am

Hi Wannes... sorry for delay in reply... please check link below.. i m facing exactly the same problem... service is hosted on IIS 7... http://forums.asp.net/t/1306010.aspx/1?Trouble+adding+a+WCF+service+reference+to+web+app+client

Wannes Geysen 18-May-11 6:10am

Ah, I'm afraid I can't help you with the ASP.NET part. I haven't worked with WCF in ASP.NET. But i suppose it should work in the same way. But apparently it doesn't. I think it is a specific ASP.NET problem. Maybe you are using specific types in the service contract that aren't supported by ASP.NET.

Wannes Geysen 18-May-11 6:14am

I have also found a similar problem at http://stackoverflow.com/questions/4621523/when-adding-wcf-service-reference-configuration-details-are-not-added-to-web-con

"I discovered how to work around this. My WCF service was implemented in its own project, and hosted in by a separate console application in the same solution. If I run the WCF service as the solution's startup project (eg. let VS host it for me) then adding the reference works fine and the correct lines are added to the client web.config. But if I host service from within my console application, while I can still add the reference, the client's web.config does not get modified. So, a workaround is to first let VS host the service, then add the reference, then change the service to be hosted (at the same address and port) in the console application.

This is surprising behaviour, and I am curious if anyone can shed any light on it?"

Vicky2Galaxy 18-May-11 6:37am

Ya... i have gone thru this.. but unfortunately this is also not helping.....as we are working with TFS and have big team.. i cant modify the things like this... i need to understand exact problem happening in my box...

Wannes Geysen 18-May-11 7:35am

So you haven't written the service yourself? You are just referencing it?

Vicky2Galaxy 19-May-11 2:53am

I have written some contracts and interface in the service.. but no change done while this problem started..everything was quite fine...

Wannes Geysen 19-May-11 5:19am

I am afraid I cannot help you any more than this. But you said you work in a big team, so probably there will be somebody who can help you.
Good luck. And if you find the answer, let me know.

Asad Naeem 21-Feb-18 0:36am

I have also found the reason in my project. Let me explain little bit here. I have two projects in my wcf service solution. first project is related to some general classes/entities. second one is wcf project. I had added a new property in one of the entities of my first project's classes but I did not add its reference again after building. I was assuming that this should work automatically but unfortunately it did not. So when I updated my reference it removed all the entity classes from my reference.cs and lots of errors appears. After following the above solution. I rebuild my first project and re-added its reference in my second project and then updated its reference again so it worked fine.