Absolutely! You can absolutely work with simple SOAP web services in Xamarin without relying on WCF — I’ve helped several devs pull off login/register flows this way. Let me walk you through how to do it step by step.

1. First, Nail Down the SOAP Request Structure #

Before coding, you need to know the exact SOAP envelope your target web service expects. You can get this from the service's WSDL, or test it directly with tools like Postman. For example, a typical login request might look like this:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <Login xmlns="http://your-service-namespace/">
      <Username>test-user</Username>
      <Password>test-pass</Password>
    </Login>
  </soap:Body>
</soap:Envelope>

Double-check the namespaces and method names — mismatches here are a super common headache.

2. Use HttpClient to Send SOAP Requests #

Xamarin's built-in HttpClient is perfect for this job, no heavy WCF libraries required. Here’s a practical example of a login function:

Login Method Implementation #

using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;
using System.Xml.Linq;

public async Task<bool> LoginAsync(string username, string password)
{
    // Build the SOAP request XML
    var soapRequest = $@"<?xml version=""1.0"" encoding=""utf-8""?>
<soap:Envelope xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:soap=""http://schemas.xmlsoap.org/soap/envelope/"">
  <soap:Body>
    <Login xmlns=""http://your-service-namespace/"">
      <Username>{username}</Username>
      <Password>{password}</Password>
    </Login>
  </soap:Body>
</soap:Envelope>";

    // Reuse HttpClient for better performance (don't create a new one every time!)
    using (var client = new HttpClient())
    {
        // Add the required SOAPAction header
        client.DefaultRequestHeaders.Add("SOAPAction", "http://your-service-namespace/Login");
        var content = new StringContent(soapRequest, Encoding.UTF8, "text/xml");
        
        try
        {
            var response = await client.PostAsync("https://your-service-url.com/Service.asmx", content);
            response.EnsureSuccessStatusCode(); // Throws if HTTP status is an error
            
            // Parse the response XML to check login success
            var responseXml = await response.Content.ReadAsStringAsync();
            var doc = XDocument.Parse(responseXml);
            XNamespace ns = "http://your-service-namespace/";
            
            // Extract the result value from the response
            var loginResult = doc.Descendants(ns + "LoginResult").FirstOrDefault()?.Value;
            return loginResult?.Equals("true", StringComparison.OrdinalIgnoreCase) ?? false;
        }
        catch (HttpRequestException ex)
        {
            // Handle network errors, service downtime, etc.
            Console.WriteLine($"Login failed: {ex.Message}");
            return false;
        }
    }
}

3. Register Function (Same Pattern, Adjusted Request) #

The registration flow follows the exact same logic — just tweak the SOAP request body to match your service's Register method:

Register Method Implementation #

public async Task<string> RegisterAsync(string username, string password, string email)
{
    var soapRequest = $@"<?xml version=""1.0"" encoding=""utf-8""?>
<soap:Envelope xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"" xmlns:soap=""http://schemas.xmlsoap.org/soap/envelope/"">
  <soap:Body>
    <Register xmlns=""http://your-service-namespace/"">
      <Username>{username}</Username>
      <Password>{password}</Password>
      <Email>{email}</Email>
    </Register>
  </soap:Body>
</soap:Envelope>";

    using (var client = new HttpClient())
    {
        client.DefaultRequestHeaders.Add("SOAPAction", "http://your-service-namespace/Register");
        var content = new StringContent(soapRequest, Encoding.UTF8, "text/xml");
        
        try
        {
            var response = await client.PostAsync("https://your-service-url.com/Service.asmx", content);
            response.EnsureSuccessStatusCode();
            
            var responseXml = await response.Content.ReadAsStringAsync();
            var doc = XDocument.Parse(responseXml);
            XNamespace ns = "http://your-service-namespace/";
            
            // Return the service's response message (e.g., "Success" or "Username already exists")
            return doc.Descendants(ns + "RegisterResult").FirstOrDefault()?.Value ?? "Unknown error";
        }
        catch (HttpRequestException ex)
        {
            Console.WriteLine($"Registration failed: {ex.Message}");
            return "Network error occurred";
        }
    }
}

Pro Tips to Avoid Headaches #

• Reuse HttpClient: Creating a new HttpClient every request can lead to socket exhaustion. Consider using a static instance or dependency injection to share one across your app.
• Validate Requests First: Test your SOAP XML with Postman or SoapUI before coding — this confirms the service accepts your request format, saving you debug time later.
• Handle Specific Errors: Expand error handling to parse SOAP fault messages (if your service returns them) for cases like invalid credentials or duplicate accounts.

I’ve used this approach in multiple Xamarin.Forms and Xamarin.Native projects, and it works reliably for simple SOAP services. Just make sure you match the service's exact namespace and method names, and you’ll be good to go.

内容的提问来源于stack exchange，提问作者Jin