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