Using Multiple Service Contracts dotnet core 3.1

Question

Access The Service Using Different Contract Or Multiple Service Contracts    I have found this link, really interesting   https://www.c-sharpcorner.com/UploadFile/c1de77/access-the-service-using-different-contract-or-multiple-serv/   i would like to know if someone has been able to reproduce it on dotnet Core 3.1             public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
app.UseEndpoints(endpoints =>
{
endpoints.UseSoapEndpoint ("/Service.svc", wsServiceBinding);
endpoints.UseSoapEndpoint ("/Service.svc/OtherService", wsServiceBinding);
endpoints.UseSoapEndpoint ("/Service.svc/OtherService2", wsServiceBinding);
});   need to  show all wsdl definition  at /Service.svc

Rajeesh Menoth · Answer

Hi,   I think the following example will help you :   https://stackify.com/soap-net-core/

dav gon · Answer

dont understand your reply sorry.
"ServiceWithMultipleContract.CompanyService"  behaviorConfiguration= "mexBehaviour" >                "ICustomerService"  binding= "basicHttpBinding"  contract= "ServiceWithMultipleContract.ICustomerService" >                 "ICompanyService"  binding= "netTcpBinding"  contract= "ServiceWithMultipleContract.ICompanyService" >                 "mex"  binding= "mexHttpBinding"  contract= "IMetadataExchange" >                                                             "http://localhost:8080"  />                        "net.tcp://localhost:8081"  />                                                                          "mexBehaviour" >                    "true"  />                         in the first link they use web.config in order to configure the behavior what i have in old project( net framework)   the project has a new version in dotnet core 3.1 and i still did not find the way to reproduce same behavior on it                      they use this line      "http://localhost:8080"  />  cant find how to setup this in the new netcore 3.1
to get this two services in same wsdl      ICompanyService, ICustomerService       regards

Rajeesh Menoth · Answer

Hi,   Just try the same one and I don't think there is no much difference of the given stack overflow solution.   Reference :   https://stackoverflow.com/questions/47171024/serve-soap-from-asp-net-core-web-method