27 Jan 2009 @ 4:13 PM 

In my last post (only this morning) I talked about an extra endpoint appearing in the WCF Test Client being the result of a rogue entry in Machine.Config, placed there when you install the .Net Services SDK.

I just noticed that this endpoint also appears elsewhere. Consider this screen capture:

image

This is the ‘Edit WCF Configuration’ screen screen that you can use to specify client and service endpoints in your App.Config / Web.Config. The only problem is that I have not defined any client end points : only service ones. And as you can see, the name is ‘sb’ which is the same name given to the end point defined in machine.config.

Funnily enough you can actually delete the endpoint from here. This causes the following to appear in your app.config:

<client>
  <remove contract=”IMetadataExchange” name=”sb” />
</client>

As a result, the endpoint no longer appears in your application. But it is still there when you run the WCF Test Client, so it still seems the only definitive way to remove it is in the machine.config file.

In the above exclude case (with the ‘remove’ statement for the endpoint) I am unsure how this will act when run on a server that does not have that endpoint defined anywhere. It will either ignore it if it doesn’t find it, or it will do something much worse.

 

 

Tags Tags: , , , , ,
Categories: Azure
Posted By: Steven Nagy
Last Edit: 10 Feb 2009 @ 06 29 PM

E-mailPermalinkComments (1)
\/ More Options ...
Change Theme...
  • Users » 76
  • Posts/Pages » 61
  • Comments » 96
Change Theme...
  • VoidVoid
  • LifeLife
  • EarthEarth
  • WindWind « Default
  • WaterWater
  • FireFire
  • LiteLight
  • No Child Pages.