-
Notifications
You must be signed in to change notification settings - Fork 562
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No endpoints compatible with .Net Core apps were found importing SAP WSDL #3565
Comments
For the record, I continued porting the Framework 4.6 version into .Net Core and despite the above warning, the Core app can call the SAP web service successfully. |
@kayakingcoder I believe you can ignore this warning in this case if it's working for you. It looks like it's showing up because your wsdl does not contain any information about your endpoint. Normal svcutil.exe doesn't generate a config file for this wsdl for the same reason, it just generates as much as it can and doesn't give you a warning about it. In dotnet-svcutil we filter out anything that isn't compatible with .NET Core, and we spit out a warning if we don't find any endpoints afterwards (in case you were expecting us to generate code related to endpoints that aren't compatible). This just means you'll need to add the information about the binding and endpoint in code yourself, which it sounds like you were already doing on your .NET 4.6 client. So I think in this case the warning message is correct that no endpoints compatible with .NET Core were found, but in reality there weren't any endpoints at all found. |
Please let us know if there is more WCF product related issue. |
Importing web service metadata ... Getting this error while adding service(SOA WSDL) to the class library. |
Importing web service metadata ... Getting this error while adding WCF Service, Please help |
I get the message "No endpoints compatible with .Net Core apps were found" when trying to import a SAP WSDL into 'n .Net Core 2.2 project .
The same service works fine in a Framework 4.6 app with the following HttpBinding.
I thought it was the same problem as Issue 8, but apparently not (as I can now see in the above code).
Below is the WSDL:
Is it possible to see what feature is not available in .Net Core and what can be done about it or what the timeframe is for getting it?
Or is there something specific I can ask the SAP team to change on their side? It's SAP R/3, which I believe is fairly old.
The text was updated successfully, but these errors were encountered: