The only other reason, the most commonly known, is changing the "contract" value with the full qualified name but you already did it... unless "Rodunu.Services.Amazon.Am
Main Topics
Browse All TopicsI'm trying to work with Amazon's Web Services. I have successfully used VS2008 to create the Service Reference. It auto generated the proxy Reference.cs and app.config files successfully.
When I execute this line:
AWSECommerceServicePortTyp
I get the error:
Could not find default endpoint element that references contract 'AmazonWebService.AWSEComm
Here is the app.config file:
<system.serviceModel>
<bindings>
<basicHttpBinding>
<binding name="AWSECommerceServiceB
openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
allowCookies="false" bypassProxyOnLocal="false"
maxBufferSize="65536" maxBufferPoolSize="524288"
messageEncoding="Text" textEncoding="utf-8" transferMode="Buffered"
useDefaultWebProxy="true">
<readerQuotas maxDepth="32" maxStringContentLength="81
maxBytesPerRead="4096" maxNameTableCharCount="163
<security mode="None">
<transport clientCredentialType="None
realm="" />
<message clientCredentialType="User
</security>
</binding>
</basicHttpBinding>
</bindings>
<client>
<endpoint address="http://soap.amazo
binding="basicHttpBinding"
contract="AmazonWebService
</client>
</system.serviceModel>
I have tried putting in the full namespace in the contract field as "Rodunu.Services.Amazon.Am
All help is appreciated.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: kaylanreilorPosted on 2008-08-13 at 22:46:12ID: 22227979
Are you working on a Windows server 2003 machine ? m/MSDN/Sho wPost.aspx ?PostID=49 6773& SiteI D=1 and referencing this blog : http://blogs.msdn.com/junf eng/archiv e/2006/08/ 09/692996. aspx
If yes, some people had issues with the config file : "For some reason, my application configuration file, normally named [Application].exe.config, must be named [Application].config on Windows Server 2003 in order for ANY configuration sections to be read (including system.ServiceModel for WCF)." here : http://forums.microsoft.co