We've started a new project using the WebApiProxy library and everything worked like a charm. But now we have deployed our Web API Project (server) to an IIS as a virtual directory, this resulted in 404 errors when calling the service from the C# client. Is it possible that the generated classes ignores virtual directories on the service?
For example: when deploying the service to the following url http:///WebApiService, the generated client classes still think the base url is http://. Or am I looking over some kind of config setting?
Hi,
We've started a new project using the WebApiProxy library and everything worked like a charm. But now we have deployed our Web API Project (server) to an IIS as a virtual directory, this resulted in 404 errors when calling the service from the C# client. Is it possible that the generated classes ignores virtual directories on the service?
For example: when deploying the service to the following url http:///WebApiService, the generated client classes still think the base url is http://. Or am I looking over some kind of config setting?