> Ensure that the proxy class generated is with the latest WSDL.
>
> Can you shed some more light on what is the solution that you are talking
> about and the exe is executed where?
>

"Kirk Allen Evans" wrote:

> Except that I just noticed you are running Compact Framework, and neither
> WSE nor WCF run on NETCF yet.
>
> I would still design this using WS-Security techniques with a UsernameToken,
> hand-crufting the UsernameToken in the NETCF serialization code, and make
> sure that you run the message over an SSL connection.
>
> --
> Kirk Allen Evans
> Developer Evangelist
> Microsoft Corporation
> blogs.msdn.com/kaevans
>
> === This post provided "AS-IS" with no warranties and confers no rights ===
> "Kirk Allen Evans" <kirke@online.microsoft.com> wrote in message
> news:363752C6-14B5-456A-8BAB-760E113810C8@microsoft.com...
> > Unable to reproduce the error. In my tests using your WSDL, the
> > parameters were serialized/deserialized in the correct order. Have you
> > been able to capture the SOAP being sent from the client to verify that it
> > is not being serialized correctly?
> >
> > As a side note, if you control the service, then strongly consider
> > changing the design to use a more secure approach. You should design this
> > with WS-Security, using WSE 3.0 or Windows Communication Foundation.
> > Either of these technologies will provide you with a better long-term
> > strategy that is much more secure and more flexible for security options
> > down the road. It is considered a bad security practice to pass the
> > password back as the result of a security call, as this can be used in an
> > attack to try to obtain other user's credentials.
> >
> > You can find more information on the WSE home page:
> >
> > http://msdn.microsoft.com/webservices/webservices/building/wse/
> >
> > You can also learn WSE by walking through a Hands On Lab exercise:
> >
> > http://www.microsoft.com/downloads/details.aspx?familyid=9acd1f8e-97e2-43e2-b484-a74a014a8206&displaylang=en
> >
> >
> > --
> > Kirk Allen Evans
> > Developer Evangelist
> > Microsoft Corporation
> > blogs.msdn.com/kaevans
> >
> > === This post provided "AS-IS" with no warranties and confers no rights
> > ===
> > "Duffcase" <Duffcase@discussions.microsoft.com> wrote in message
> > news:14F804A3-98E4-4423-B6F0-DE0627F674CB@microsoft.com...
> >>> Ensure that the proxy class generated is with the latest WSDL.
> >>>
> >>> Can you shed some more light on what is the solution that you are
> >>> talking
> >>> about and the exe is executed where?
> >>>
> >>
> >> Thanks for your reply.
> >>
> >> The proxy class is from the latest WSDL.
> >> The .exe is executed in a windows xp environment, forgot to mention that.
> >>
> >> The solution is a document/literal web service that is supposed to log a
> >> user in. The client supplies a username and a password.
> >>
> >> The code for the client:
> >>
> >> MainController service = new MainController();
> >> service.Url = "http://10.0.102.112:8080/trim/ws";
> >>
> >> try
> >> {
> >> checkUserAccessLogin login = new checkUserAccessLogin();
> >> login.String_1 = brukernavn.Text;
> >> login.String_2 = passord.Text;
> >>
> >> checkUserAccessLoginResponse response =
> >> service.checkUserAccessLogin(login);
> >> Users user = response.result;
> >>
> >> }
> >> catch (Exception ex)
> >> {
> >> MessageBox.Show("ERROR: " + ex.Message);
> >> }
> >>
> >> relevant parts of the WSDL:
> >>
> >> <complexType name="checkUserAccessLogin">
> >> −
> >> <sequence>
> >> <element name="String_1" nillable="true" type="string"/>
> >> <element name="String_2" nillable="true" type="string"/>
> >> </sequence>
> >> </complexType>
> >>
> >> <element name="checkUserAccessLogin" type="tns:checkUserAccessLogin"/>
> >>
> >> <complexType name="Users">
> >> −
> >> <sequence>
> >> <element name="address" nillable="true" type="string"/>
> >> <element name="cellPhone" nillable="true" type="string"/>
> >> <element name="email" nillable="true" type="string"/>
> >> <element name="firstName" nillable="true" type="string"/>
> >> <element name="groupID" nillable="true" type="int"/>
> >> <element name="homePhone" nillable="true" type="string"/>
> >> <element name="isActive" type="int"/>
> >> <element name="isAdmin" type="int"/>
> >> <element name="isDeleted" type="int"/>
> >> <element name="language" nillable="true" type="string"/>
> >> <element name="lastIP" nillable="true" type="string"/>
> >> <element name="lastLogin" nillable="true" type="string"/>
> >> <element name="lastName" nillable="true" type="string"/>
> >> <element name="position" nillable="true" type="string"/>
> >> <element name="postNo" nillable="true" type="string"/>
> >> <element name="postRegion" nillable="true" type="string"/>
> >> <element name="userID" nillable="true" type="int"/>
> >> <element name="userName" nillable="true" type="string"/>
> >> <element name="userPass" nillable="true" type="string"/>
> >> <element name="workPhone" nillable="true" type="string"/>
> >> </sequence>
> >> </complexType>
> >>
> >> </types>
> >> −
> >> <message name="MainControllerInterface_checkUserAccessLogin">
> >> <part element="ns1:checkUserAccessLogin" name="parameters"/>
> >> </message>
> >>
> >> <operation name="checkUserAccessLogin">
> >> <input message="tns:MainControllerInterface_checkUserAccessLogin"/>
> >> <output
> >> message="tns:MainControllerInterface_checkUserAccessLoginResponse"/>
> >> </operation>
> >>
> >> <soap:binding style="document"
> >> transport="http://schemas.xmlsoap.org/soap/http"/>
> >> −
> >> <operation name="checkUserAccessLogin">
> >> <soap:operation soapAction=""/>
> >> −
> >> <input>
> >> <soap:body use="literal"/>
> >> </input>
> >> −
> >> <output>
> >> <soap:body use="literal"/>
> >> </output>
> >> </operation>
> >>
> >> hope this helps.
> >>
> >>
> >>
> >