Hi,
I have an interesting problem with my RPC encoded webservices. When I
upgrade to Framework 1.1, I get the following error when calling my web
methods.
[Server was unable to process request. --> File or assembly name
kmcuficw.dll, or one of its dependencies, was not found.]
After a bit (make that quite a bit) of investigation I discovered that the
problem only occurs when the SOAP message style is rpc/encoded. (ie using
the [System.Web.Serv ices.Protocols. SoapRpcService] attribute). After
playing around a little more, I then discovered that the problem only occurs
when I have an optional value type defined in my schema.
For example.
<xs:element name="CountryID " type="xs:int" minOccurs="0" maxOccurs="1" />
autogenerated class
[System.Xml.Seri alization.XmlTy peAttribute(Nam espace="http://tempuri.org/MyCountries.xsd ")]
public class Country {
/// <remarks/>
public int CountryID;
/// <remarks/>
[System.Xml.Seri alization.XmlIg noreAttribute()]
public bool CountryIDSpecif ied;
/// <remarks/>
public string Name;
}
To summarise everything is fine running under v1 of the framework. When
running under framework 1.1 everything works when I either a) remove the
[System.Web.Serv ices.Protocols. SoapRpcService] attribute.
b) leave the [System.Web.Serv ices.Protocols. SoapRpcService] attribute as is
but do not use optional fields.
None of these options are satisfactory as this is a production environment
and my clients wont be happy if I change the WSDL.
Any help on this will be greatly appreciated.
Kind Regards
Paul
I have an interesting problem with my RPC encoded webservices. When I
upgrade to Framework 1.1, I get the following error when calling my web
methods.
[Server was unable to process request. --> File or assembly name
kmcuficw.dll, or one of its dependencies, was not found.]
After a bit (make that quite a bit) of investigation I discovered that the
problem only occurs when the SOAP message style is rpc/encoded. (ie using
the [System.Web.Serv ices.Protocols. SoapRpcService] attribute). After
playing around a little more, I then discovered that the problem only occurs
when I have an optional value type defined in my schema.
For example.
<xs:element name="CountryID " type="xs:int" minOccurs="0" maxOccurs="1" />
autogenerated class
[System.Xml.Seri alization.XmlTy peAttribute(Nam espace="http://tempuri.org/MyCountries.xsd ")]
public class Country {
/// <remarks/>
public int CountryID;
/// <remarks/>
[System.Xml.Seri alization.XmlIg noreAttribute()]
public bool CountryIDSpecif ied;
/// <remarks/>
public string Name;
}
To summarise everything is fine running under v1 of the framework. When
running under framework 1.1 everything works when I either a) remove the
[System.Web.Serv ices.Protocols. SoapRpcService] attribute.
b) leave the [System.Web.Serv ices.Protocols. SoapRpcService] attribute as is
but do not use optional fields.
None of these options are satisfactory as this is a production environment
and my clients wont be happy if I change the WSDL.
Any help on this will be greatly appreciated.
Kind Regards
Paul