Stephen Bonikowsky

icon company @Microsoft

Results 58 comments of Stephen Bonikowsky

Old SOAP service (web reference) - throwing 'Message {nameOfFunction} must not have headers to be used in RPC encoded style.'

@dasetser Tooling related, could you provide @hurrk some guidance or more info about the error he got?

Old SOAP service (web reference) - throwing 'Message {nameOfFunction} must not have headers to be used in RPC encoded style.'

@hurrk and @mottykohn let us know if this doesn't work for you.

Old SOAP service (web reference) - throwing 'Message {nameOfFunction} must not have headers to be used in RPC encoded style.'

@mottykohn Sorry for the delay in getting back to you. We are having to focus on some other high priority work so we haven't been able to follow-up on this....

Old SOAP service (web reference) - throwing 'Message {nameOfFunction} must not have headers to be used in RPC encoded style.'

@hurrk Thanks for the additional info. We are going to look into this. We just have to do some load balancing, but it is in our short list of issues...

Old SOAP service (web reference) - throwing 'Message {nameOfFunction} must not have headers to be used in RPC encoded style.'

PR merged, closing.

NRE when response has Content-Type but empty body

Thanks for reporting this @IGx89 we'll have someone take a look next week.

NRE when response has Content-Type but empty body

@mconnew did this issue get fixed as a side-effect of PR #3709?

NRE when response has Content-Type but empty body

This looks like it would be a simple fix. We should consider it for 5.0.

Client Proxy generated for wsdl with minOccurs=0 for value types.

@gt5700 Thanks for reporting this! We are working on the current release of the tool, we will look at this issue for the next release.

Could not load type 'System.ServiceModel.Description.MetadataConversionError

@HASSEN-MEDDEB-ATOS I'm not sure what update you are asking for, I mentioned in my previous post that you are trying to use a type that is not supported in WCF...