Matt Connew

I need to write the client implementation too and that will be released at the same time as .NET7 so current plan is around November time.

I've made a special label to group all the wsdl issues so that I can address as many as possible when I revisit wsdl's soon.

@itsalexjones, are you still having a problem with this? If so, can you send me the repro to my email? My email address is my username at the microsoft.com domain.

Can you please verify that you don't see this issue when using a .NET Framework WCF client and that this is a regression? When an XML element isn't being output...

@bogatykh, it's not an issue in corefx. I checked the result from `ReadAsStringAsync` and the spaces are there. I also tested the repro from above on NetFx and the spaces...

Can you confirm that this worked on .NET Framework? The exception is coming from System.Configuration and I don't think any of the changes between WCF and CoreWCF come into play...

I would be open to having this be built in. My only criteria with the implementation is that it's pay to play. That is, if you aren't using App Insights,...

App Insights support is based off of open telemetry now. So that should be fine.

Transport – NamedPipe

Transport – Msmq This would also include making the MSMQ communication generic to message queue's in general but would include a concrete MSMQ implementation.