Hi Manohar, and thanks for the response.
1. Use the proxy type as-is. Since this was generated class, it will be
close to what the web service returned, sans any methods.
My custom class is very simple. Two private fields. Two properties to
read-access the private fields. Two constructors (default, and one that
sets the two fields' values).
Are you saying that the proxy type will contain the data that my custom
class contains , but the two properties will not be available ?
So, I access the data like this:
2. Manually edit the proxy class (found in webreferences folder of your web
site, with the same name as the reference page), and remove the proxy type,
and include the actual type in the cs file. Then add the corresponding using
statement as well.
I'm not sure exactly what to do here.
Looking at my web-application in Visual Studio, and clicking on the
web-reference, a number of expandable nodes are shown: these appear to be
all of the types that my web-service references. Among them is listed the
name of my custom class -- but the first character is in lower case. In the
tree that expands from that node are listed my class' fields, construtors,
and properties exactly as I've defined them.
I'm looking at the contents of the "Web References" folder underneath my
web-app's physical folder: Reference.cs, Reference.map,
These files all look very dangerous to edit.