SSL on Compact Framework Application

[timp]

Hi

I am trying to request a web service from an IIS server via https within a
pocket pc windows application. The IIS web service has been configured to use
SSL. This web service is just a simple HelloWorld program, which returns a
string when called. ICertificatePolicy interface is implemented on the pocket
pc application so that it will accept all certificates when an https request
is made.

Initial test on a seperate ASP.NET application on desktop browser and pocket
pc application using an emulator (Pocket PC 2003) to connect to web service
does not generate any errors.

Code snippet of the web service client proxy file (Generated by
VisualStudio.Net 2003 in Reference.cs file) as follow:

--------------------------------------------------------------------------------------------
public Service1()
{
this.Url = "https://192.168.0.116/webservice_add/Service1.asmx";
}

[System.Web.Services.Protocols.SoapDocumentMethodAt tribute("http://tempuri.org/HelloWorld",
RequestNamespace="http://tempuri.org/",
ResponseNamespace="http://tempuri.org/",
Use=System.Web.Services.Description.SoapBindingUse .Literal,
ParameterStyle=System.Web.Services.Protocols.SoapP arameterStyle.Wrapped)]
public string HelloWorld()
{
object[] results = this.Invoke("HelloWorld", new object[0]);
return ((string)(results[0]));
}

--------------------------------------------------------------------------------------

However, when this application is deployed and executed on a pocket pc
device (Dell Axim X30, Windows Mobile 2003 based-Pocket PC with .Net Compact
Framework SP3), it generates an exception causing the application to crash.
This happens when the web service is called, (when this.Invoke("HelloWorld",
new object[0]) is called). I have tried to catch the error but no avail.

The application generates an exception as follow:

A native exception has occurred in HelloWorldClient.exe.
The details of the exception are as follow:

ExceptionCode: 0xc0000005
ExceptionAddress: 0x00df5c00
Reading: 0x2e7d0050

Any idea or solution to this exception?

Thanks.

--
timp