Unable to Import WSDL (Metadata contains a reference that cannot be resolved)

[rjts]

VS 2017 Targetting .Net Standard 2.0 or .Net Core 2.0
I tried the Connected Services - Microsoft WCF Web Service Reference Provider and it generates the error below...
I also tried the command line version of the same thing and it too reports a CData error as before.
If I change the project type to .Net Framework 4.6.2 which seems to use the old svcutil app - this does succeed but I need it to work with .Net Core 2.0.

Suggestions, workarounds or ideas appreciated.

This is the error. The WSDL is publically available if you want to try importing.

An error occurred while attempting to find services at 'http://files.developer.sabre.com/wsdl/sabreXML1.0.00/PPP/6.35/EPS_ProfileCreateRQ.wsdl'.
CData elements not valid at top level of an XML document. Line 1, position 3
Sub Error...
Metadata contains a reference that cannot be resolved: 'http://files.developer.sabre.com/wsdl/sabreXML1.0.00/PPP/6.35/xml.xsd'.

[rjts]

Fyi: I've sent a support request to the Sabre developers in case its a schema issue in a sub file. I'll update this if I get a response. As well as it working with the .Net Framework 4.6.2 svcutil app, I also double checked it with the really old wsdl.exe app and that works as well.

[sameera]

@rjts Could you be experiencing the same thing as: #2197 ?
The fix is in VS 15.6 Beta or use the dotnet-svcutil as described in the thread.

[rjts]

Thanks - I'm was using VS 15.5.6

1. Downloaded and tried with VS 15.6.0 Preview 4.0 - It generates exactly the same error.
2. I tried the command line version and it too generated the same error.

[mlacouture]

@rjts thank you for reporting this issue. A fix for this issue is available in Visual Studio 2017 v15.6-Preview 4, I hope you can try the preview.

[rjts]

I Downloaded and tried with VS 15.6.0 Preview 4.0 - It generates exactly the same error.
I tried the command line version and it too generated the same error.

So no the "fix" didn't seem to correct the issue.

[mlacouture]

@rjts, you are right, the fix is not yet available, it will actually be available with the release of Visual Studio 2017 v15.7 Preview 1, currently scheduled to ship around March 7. Sorry for the confusion.