>This is the same issue I've faced some months ago: .NET doesn't *not* use the same Soap Client as VFP; instead, it access Web Services natively by means of classes contained in the Framework. I haven't had the chance to solve the problem by that time.

Then, it means the native functionality not does comply to the Soap Client 3. We'll have to wait for an update of version.