EndpointNotFound exception on Silverlight Web App, hosted on IIS - wcf

Question

Once again I hope you can assist with a problem I can't figure out.
I have a Silverlight web app that used to work and after making changes to the code, adding some WCF methods and updating tables on an MS-SQL database, it has stopped working and I cannot figure out why.
The web app runs on Windows 7 hosted in the default IIS.
When running through Visual Studio it works fine, but not when running from the web page.
I know it has something to do with the Enpdoint, but what is strange is that I didn't change anything there. It runs from the same site on IIS.
The WCF trace:
Exception.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=4.0.0, Culture=neutral, PublicToken=b77a5c561934e089
I am not all that familiar with Silverlight so cannot figure out what has changed or what I broke.
A portion of Web.config:
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior name="">
<serviceMetadata httpGetEnabled="true"/>
<serviceDebug includeExceptionDetailInFaults="true"/>
</behavior>
</serviceBehaviors>
</behaviors>
<bindings>
<customBinding>
<binding name="HSCGym.Web.GymRebateService.customBinding0" receiveTimeout="00:10:00" sendTimeout="00:10:00" openTimeout="00:10:00" closeTimeout="00:10:00">
<binaryMessageEncoding/>
<httpTransport/>
</binding>
</customBinding>
</bindings>
<serviceHostingEnvironment aspNetCompatibilityEnabled="true" multipleSiteBindingsEnabled="true"/>
<services>
<service name="HSCGym.Web.GymRebateService">
<endpoint address="" binding="customBinding" bindingConfiguration="HSCGym.Web.GymRebateService.customBinding0" contract="HSCGym.Web.GymRebateService"/>
<endpoint address="mex" binding="mexHttpBinding" contract="IMetadataExchange"/>
</service>
</services>
</system.serviceModel>
If I break and check the EndPoint Uri address, it shows incorrectly:
http://localhost:8080/rebate/ebate/GymRebateService.svc
Any ideas as to what I am doing wrong?
Neill

Answer 1

The issue is that you haven't told your web service where its end point is so it will use the one that you created it with which was most likely localhost.
Here is a bit of code I use to automatically switch between localhost and server so I don't have to remember to do it when deploying
string ServerPath = App.Current.Host.Source.AbsoluteUri.Replace(App.Current.Host.Source.AbsolutePath, "");
string ServicePath = ServerPath + "/Services/YOURSERVICENAME.svc";
var myBindings = new BasicHttpBinding();
myBindings.Security.Mode = BasicHttpSecurityMode.None;
myBindings.MaxReceivedMessageSize = int.MaxValue;
var address = new EndpointAddress(ServicePath);
App.GlobalVars.service = new RIFTRunComparerServiceClient(myBindings,address);