When importing some WSDLs, not all proxy classes are created in .net core 1.1 / VS2017 Community
See original GitHub issueAs an example, I have imported a WSDL from a salesforce enterprise account and am missing certain classes and properties. For example: SessionHeader class is missing, which is required by the salesforce api. Interestingly enough, if I open my older VS2015 targeting .Net 4.5 and add the same wsdl, I get the required classes and properties. I have attached the problematic wsdl file so you can see the issue.
salesforce_wsdl.docx
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
Failing to generate proxy from WSDL in VS2017
1 Answer 1 · The first try was to add service reference from the local WSDL files, when this did not work I...
Read more >Unable to use a WSDL file to generate proxy: "The service ...
I'm trying to generate a proxy using the extension "Microsoft WCF Web Service Reference Provider" for VisualStudio 2017 to be used in dotnet...
Read more >Add Service Reference does not generate proxy/client ...
It works fine if I use Visual Studio 2019. The project where I am trying to create the proxy/client was created using the...
Read more >Integrating with SOAP web services in .NET Core
This blog post will have a look at how we can start of with a WSDL (Web Services Description Language) file, generate C#...
Read more >Unable to load asp.net core project in VS2017 ...
I use VS2017 15.8.3 to open an asp.net core project, and got a "project file is incomplete. expected imports is missing" error.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@Adrian10988 We have enabled MessageHeader in the latest release.
@Adrian10988 I tried that, but didn’t work. So sad. =(