Error : Could not find default endpoint element

Performance freak
Search for a command to run...

Performance freak
No comments yet. Be the first to comment.
When you use Response.Redirect with its second parameter set to true, it triggers a call to Response.End() Response.Redirect("Login.aspx"); // default is true Response.Redirect("Login.aspx", true); // same as above This causes AS...

Using ThreadPool.QueueUserWorkItem: Helps bypass limitations when trying to run async code inside IHttpModule. Does not interfere with the ASP.NET pipeline. Email sending does not block the main thread. Calling SendMailAsync().Wait() is safe here...

Introduction In SQL Server, the bit data type is used to store boolean values (0 for false, 1 for true). However, when working with SQL Server in a .NET application using Entity Framework or LINQ to SQL, the bit field is automatically converted to a ...

System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() To avoid the ThreadAbortException error when using Response.Redirect, setting the second parameter to false is generally sufficient. However,...

In Visual Studio; Solution Explorer-Project-Properties-Application. Check "Auto-Generate binding redirects" When this is selected, versions are specified in the web.config file after the Nuget package updates. When is binding necessary? If there is...

Error :
Could not find default endpoint element that references contract 'XXX.xxx' 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.
This error can arise if you are calling the service in a class library and calling the class library from another project.
If you are using web app, then you have to copy app.config of class library configuration content to web.config of web project.
Here is the config details. It contains bindings and client nodes.
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="smsnnPortBinding" />
</basicHttpBinding>
</bindings>
<client>
<endpoint address="http://api.google.com/SMS"
binding="basicHttpBinding" bindingConfiguration="smsnnPortBinding"
contract="XXX.xxx" name="smsnnPort" />
</client>
</system.serviceModel>
Be careful, contract="XXX.xxx" name must be same as error indicated