By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,694 Members | 1,882 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,694 IT Pros & Developers. It's quick & easy.

how to use a form of latebinding with webservices ??? and a .netclient

P: n/a


scenario :

I had a remoting server , now this remoting server needed the ability to
comunicate with a Delphi 5 client, so i got the advise to switch to
webservices

now i rebuilded the Cassini webserver , so i can deploy it and
everything works fine

However i have one problem , and this is with my own .Net clients cause
i do not know how i get them late binded to a webserver ( on compile
time i never know where the server is )

i am able to do this with VB6 but i don`t know how to do it with VB.Net
:-( as far as i know you must set a reference in the development
stage with VB.Net however my app is beeing deployed so i never know what
the uri of the webservice is ofcourse the interface is alway`s the same
can someone point me in the right direction ??

Michel
Nov 23 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hello M.Posseth,
Instead of using add web reference try using the wsdl command like below

wsdl.exe /l:VB /out:proxy.vb http://localhost/service.asmx?wsdl /appsettingurlkey:myurl

This is generate code that would look like this...

theProxy.Url= System.Configuration.ConfigurationSettings.AppSett ings ("myurl")

You would need to add a key to your client configuration file like this...

<appSettings>
<add key="myurl" value="http://hostname/service.asmx" />
</appSettings>

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com
scenario :

I had a remoting server , now this remoting server needed the ability
to comunicate with a Delphi 5 client, so i got the advise to switch
to webservices

now i rebuilded the Cassini webserver , so i can deploy it and
everything works fine

However i have one problem , and this is with my own .Net clients
cause i do not know how i get them late binded to a webserver ( on
compile time i never know where the server is )

i am able to do this with VB6 but i don`t know how to do it with
VB.Net :-( as far as i know you must set a reference in the
development stage with VB.Net however my app is beeing deployed so i
never know what the uri of the webservice is ofcourse the interface
is alway`s the same

can someone point me in the right direction ??

Michel


Nov 23 '05 #2

P: n/a
Dilip Krishnan wrote:
Hello M.Posseth,
Instead of using add web reference try using the wsdl command like below

wsdl.exe /l:VB /out:proxy.vb http://localhost/service.asmx?wsdl
/appsettingurlkey:myurl

This is generate code that would look like this...

theProxy.Url= System.Configuration.ConfigurationSettings.AppSett ings
("myurl")

You would need to add a key to your client configuration file like this...

<appSettings>
<add key="myurl" value="http://hostname/service.asmx" />
</appSettings>

HTH
Regards,
Dilip Krishnan
MCAD, MCSD.net
dkrishnan at geniant dot com
http://www.geniant.com
scenario :

I had a remoting server , now this remoting server needed the ability
to comunicate with a Delphi 5 client, so i got the advise to switch
to webservices

now i rebuilded the Cassini webserver , so i can deploy it and
everything works fine

However i have one problem , and this is with my own .Net clients
cause i do not know how i get them late binded to a webserver ( on
compile time i never know where the server is )

i am able to do this with VB6 but i don`t know how to do it with
VB.Net :-( as far as i know you must set a reference in the
development stage with VB.Net however my app is beeing deployed so i
never know what the uri of the webservice is ofcourse the interface
is alway`s the same

can someone point me in the right direction ??

Michel


Aha thanks Dilip
In the meanwhile i discovered that if you choose show all files in the
project tab you can also find there the proxy class that .Net generates
behind the scenes with some slight tweaking ( like adding a property for
the URL ) this can be easily converted in a "late" binded proxy class
( already played with it )

i will investigate the class that the wsdl.exe tool generates also
thanks for your help
Michel [MCP]
Nov 23 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.