I am writing a Windows service in ASP.NET Core 5 that hosts web service API's (i.e. controllers).
At the end of the startup sequence, I would like write to the log file a list of all web service API URL's that exist in the service. Is there a way to programmatically find and list all valid web service API's?
I have a task to Upload and Download a word file from the microsoft ONEdrive using WCF service. I there is a possiblity to do that. Can doing the authentication through WCF service is easy without the interaction with user. Everything should be done in the background.
Regards,
Rajesh
I have successfully deployed my WCF restful web service to IIS 7. I have verified that my service is working when I call it from a browser in IE via a something like "https://myserver/mservice.svc/postuser/JohnSmith" . The method is a POST and I have verified that my IIS configuration allows for POSTS.
My issue is as follows. We are using a 3rd party Software as a Service application that allows for external web service calls. It allows you to configure the URL "https://myserver/mservice.svc/postuser/" and then you can choose a parameter. When I call the web service from the external application, a 404 error is registered in IIS.
I think there must be some difference between the way I call my webservice "https://myserver/mservice.svc/postuser/JohnSmith" and the way the SAAS application is calling my external web service. The web service is attempting to pass the username, but I cannot detect how it is constructing this.
Do I need to write a web enabled front end for my web service that is hosted in IIS that can handle XML? I'm assuming this is how the SAAS application is trying to pass the username onto my web service.
Thank you all in advance for your ideas and help.
What is the difference between developing WCF service by opening a console application project(generally) and a WCF project? By creating a WCF service project, the auto generated files consist of app_data, IService1.cs , Service1.svc and web.config. What is the purpose of those files?
thanks!
a WCF service project is a web project designed to run in IIS.
The web.config file contains the configuration of the web app (and the WCF service configuration -endpoint, behaviors, bindings)
The svc file is the web resource your client will call, it associates an url (service1.svc) with a service contract.
The IService1.cs file contains the service contract interface.
there is a Service.svc.cs file too which contains the service contract implementation.
If you use WCF in a console project, you will have to start WCF yourself (ServiceHost etc...)
If you use WCF in a web application, this logic is handled by the service activation framework in IIS, using the configuration provided by web.config.
IIS activated WCF services are easier to use, but require to be hosted by the web server.
Uploading and downloading files using wcf data services?
How can we implement this on the wcf data service end and using html+jquery as client?