Wcf Winforms-specific endpoint error?

Up vote 0 down vote favorite share g+ share fb share tw.

I've written a WPF UserControl that accesses a rudimentary WCF Service. The service is up and running fine and all of the operations work. The endpoint issues started when I moved my UserControl out of the client's project and into a WPF User Control Library.

I first had a basic test WPF application client and ran into the "endpoint not found" issue, which eventually I solved by copying over the binding and endpoint xml into my client's app. Config file. I thought I was done, but the control will also likely be used in a WinForms app, so I made a simple WinForms app to test it out.

The issue is that when I try to drop the UserControl into the WinForms designer, I get that same "endpoint not found" error. The conditions are EXACTLY the same between WPF and Winforms (i. E same config file and references), but it works perfectly in WPF and has that blasted error in Winforms.

Is there anything specific to Winforms that complicates WCF? I'm really at a loss for what to do... Here is my config file if that helps: wpf winforms wcf endpoint link|improve this question asked Jun 30 '11 at 0:15Joe11.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.