visual studio vs 10 RC Could not find default endpoint element that references contract WcfPortal.IWcfPortal in the ServiceModel client configuration section

visual studio vs 10 RC Could not find default endpoint element that references contract WcfPortal.IWcfPortal in the ServiceModel client configuration section

Old forum URL: forums.lhotka.net/forums/t/8745.aspx


AaronH posted on Wednesday, March 31, 2010

Wondering if anyone is using VS10 RC, CSLA SL, targeting SL 3.0.  Here is the scenario:

1.) Download 3.8.2 samples

2.) Open RemotePortalWithCompressedProxy with VS10 and allow it to convert.

3.) Remove the broken references to CSLA and CSLA SL

4.) Add the 3.8.2 CSLA and CSLA SL projects to the solution - convert as well

5.) Create project references between the existing projects in the solution to the CSLA projects.

6.) Build and run (it will build just fine)

I receive the following exception:

Could not find default endpoint element that references contract 'WcfPortal.IWcfPortal' in the ServiceModel client configuration section. This might be because no configuration file was found for your application, or because no endpoint element matching this contract could be found in the client element.

Any thoughts?  I've been at this on and off for weeks now.  Unfortunately, I am having the same issue with my production project code, which disallows me from stepping through the CSLA code.  Fortunately I can get my code to run if I reference .dll's rather than project references, but then I do NOT get to walk through CSLA code, which I need to do to fix some bugs (for some reason, my pdb's are being ignored as well).

Any thoughts or related experiences would be greatly appreciated!

RockfordLhotka replied on Wednesday, March 31, 2010

Try dropping the "Csla." off the start of the contract name so it looks like this

contract="WcfPortal.IWcfPortal"

I had to do this to my clientconfig files to get things to work in VS10. I assume it is a bug in WCF, or perhaps a "feature" of some sort - but for some reason using the full namespace doesn't work anymore.

AaronH replied on Wednesday, March 31, 2010

Ok, that helped get past the original exception.  But now it can't find a matching endpoint.

The remote server returned an error: NotFound. 

It's weird, in the WcfProxy.GetProxy() method, the following check is made:

if (!string.IsNullOrEmpty(this.DataPortalUrl) && this.Binding != null)

In my case, this.DataPortalUrl is always null.  (Even before I removed the "CSLA" from the contract in teh ClientConfig.  Not sure why.  I'll keep cracking at it and update on my progress...

Copyright (c) Marimer LLC