WCF works in C# environment but not in VB...

Question

3.00/5 (1 vote)

See more:

Good morning all,
I have a really strange problem that I can not fix nor understand.
I have a WCF service (C#), wrapped in a class for more convenient use that was tested and worked fine.
This wrapper runs in a C# test environment and performs as expected.
The test-form instantiates the wrapper and contains a button that brings up a TestClient which sends a message to the service.
Nothing special so far. Everything works fine, the service receives the message and prints it to the console.

I then recreated the test-form with VB.NET (our main environment is VB so this was necessary). It is exactly the same setup as the C# test-form (just an instance of the wrapper and a button to bring up the TestClient-Form). But the client-form opened by the button always fails with a receive-timeout, regardless how long this timeout is defined.

When I launch the testclient on its own (without having the test-form open it by clicking the button) everything works fine. Also if I put the service-wrapper into a background-thread or open it via process.start everything works fine.

It is just the VB test-form in VB only (C# always works) that fails if it openes the test-client via the button click.

I also used the WcfTestClient.exe tool and the service is always there, regardless of the testenvironments language.

I asked this in the WCF forum too, but unfortunately we couldn't find the cause for this behavior (http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/876c41e7-9502-4e90-ac81-640e10b235bc/[^])

Now I really hope somebody is out there having an idea about whats going on here. I could workaround this by using the background thread approach, but I am really interested in understanding the real problem to get it solved.

Any hints, ideas or comments are kindly appreciated.

best regards
Andy

Posted 17-Nov-10 20:38pm

hoernchenmeister

Add a Solution

Comments

Dalek Dave 18-Nov-10 4:55am

Good and unusual question!

hoernchenmeister 18-Nov-10 5:38am

Thanks Dave ;)
...this bugs me for days already :(

hoernchenmeister 22-Nov-10 2:43am

Nobody? Not a single idea?
I can provide Testprojects to reproduce this behavior if necessary...

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)

Abhinav S · Answer 1 · 2010-11-17T21:01:00

Solution 1

Check if the service configuration file is different in both the cases.

Posted 17-Nov-10 21:01pm

Abhinav S

Comments

hoernchenmeister 18-Nov-10 3:15am

The service configuration is always the same. I just copied it from the C# test-environment to the VB test-environment. Also the TestClient.config resides within the same directory as the C#/VB Test-App.