Why is reference.vb hierarchally linked to reference.map?
- From: "Richard Myers" <fake@xxxxxxxxxxx>
- Date: Fri, 6 May 2005 22:18:21 +1200
Hello.
When generating a webservice proxy i notice that reference.vb is
heirarchally linked to reference.map.
Why is this since if i delete reference.map and re-include reference.vb my
project compiles and runs just fine?
Ive done a liitle reading on msdn about this but this has left me with the
understanding that ref.map is basically just a discovery log.
It doesn;t seem to have any runtime purpose at all? At least not post proxy
generation? I dont even want most of this guff including the wsdl most of
the time once my proxy has been generated and i surely cant see what
purpose it serves (ref.map) nor why it is linked in this way?
Any thoughts?
Richard
.
- Follow-Ups:
- Re: Why is reference.vb hierarchally linked to reference.map?
- From: Brock Allen
- Re: Why is reference.vb hierarchally linked to reference.map?
- Prev by Date: Dynamic binding in webservices
- Next by Date: Consume RPC/Encoded webservice from ASP.NET double,integers,boolean problem
- Previous by thread: Dynamic binding in webservices
- Next by thread: Re: Why is reference.vb hierarchally linked to reference.map?
- Index(es):