Docs: Next Steps? What are those?

[ThaDaVos]

What are the next steps? It's just empty...

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0e89651a-5ad9-c3f9-146f-8d87b87d9e11
• Version Independent ID: 85c0e55f-abc0-3b2d-409a-06042b1f3ebb
• Content: Microsoft WCF Web Service Reference Provider Tool
• Content Source: docs/core/additional-tools/wcf-web-service-reference-guide.md
• Product: dotnet-core
• GitHub Login: @mlacouture
• Microsoft Alias: johalex

[rpetrusha]

Thanks for your feedback, @dvdbot. The Next Steps section isn't empty; it has two subheads, Feedback & questions and Release notes.
Since the section is not empty, I'll close this issue.

[MattiasTR]

This one should really be reopened. "Next steps" should not be "Feedback & questions" and "Release notes", it should point to places where people can find information on how to proceed to use the WCF for .NET Core.

[mairaw]

Done. @mlacouture let us know if you’d like to add any next steps. Otherwise, we should just remove that heading and move the Sub-sections one level up.

[Jungers42]

I, for one, would appreciate knowing a great deal more about "When these processes complete, you can create an instance of the generated WCF client type and invoke the service operations." .... I'm going to now go spelunking to figure out how to go about that ... which is precisely what I would have expected to be include in the "Next Steps" section. Release notes and feedback are NOT useful next steps for someone who's actually trying to use the built services within .NET Core / Standard.

[mlacouture]

@Daniel [e-mail] fyi.

[Jungers42]

In the end, it was simple enough, but some quick samples would be the norm for something like this just so folks know they're on the right track or not. And, as was the case for me, I needed to deal with some painful WSS security header shenanigans. I'm not sure how common that is, but it took most of the day to figure out how to build out my own security header, inspector, and get everything working for .NET Core (followed the breadcrumbs laid out for me starting here: https://stackoverflow.com/questions/48625444/calling-a-soap-service-in-net-core ). So having a collected example of this would be really helpful (especially because that kind of capability is, for some crazy reason, explicitly not supported directly within .NET Core).

[nissimlevy]

What are the next steps? How do I use this WCF Web Service Reference Provider?

[steepho]

How do I use my reference once its added? Does anyone have any code examples?
I tried ServiceRefernce1 _sr1 = new ServiceRefernce1(); but i get a little Red X in intellisense when adding the ServiceRefernce1() part and the error is ('ServiceReference1' is a namespace but used like a type.)

Help please!

[Dongata]

Would be great a guide on how to add authorization, unsing DI, how it's expected to be consumed

[RussianDragon]

What next?
How use?
How correct add service in dependency injection?
How set proxy address?
Maybe simple example?

[fivepoint-0]

Can an example be put on the page? How do I invoke the service properly? How do I know if my WSDL warnings will impact the service I'm implementing/invoking? I would feel more confident I'm doing things correctly for the first part of the implementation if there was information on utilizing an example sample service in code.