16,013,747 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View .NET questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by BugRaptor (Top 2 by date)
BugRaptor
28-Apr-15 15:52pm
View
Thank you for your answer.
I finally solved the communication issue by the following corrections:
1) On the Client side, my App.config file refered a wrong endpoint address.
2) On the server side I published the WCFServiceLibrary1 on http://localhost, I had to publish it in the refered /WebSite folder: http://localhost/WebSite
3) After these fixes, I didn't got the EndpointNotFoundException anymore, but I got a ProtocolException Unhandled, (405) Method not allowed when the Client tried to invoke a WCF service method.
I finally found this was due to a configuration issue in my .Net 4.5 platform: The HTTP Activation feature was not enabled !
Now the WCF calls finally work properly.
Thank you for your help.
BugRaptor
26-Apr-15 13:25pm
View
I simply published it from VS to my iis 8 Web Site.