WinForms and WebServices

  • Thread starter Thread starter Johnny Jörgensen
  • Start date Start date
in Johnny J. wrote :
Now I need to program the accompanying Winforms app. To be able to
use the methods and properties of the service I HAVE TO add a web
reference to the service in the application references and the VS
guide that helps you doing that has to be able to access the service
itself to list it's methods and properties.
This is not possible because the service is not installed live
anywhere. So I cannot add the web reference and thus I cannot create
a web service object instance and use the web service methods and
properties in the app.

What is your developpment IDE ? With VS, just put the two projects in
the same solution and you will be able to generate the proxy class
without installing the web service.

If you can't do that. Install the web service somewhere (local IIS for
example if you have XP pro) and build the proxy class from the local
url.

Then you just have to change this url at runtime to address the actual
location of the service.
 
in Johnny J. wrote :
Now I need to program the accompanying Winforms app. To be able to
use the methods and properties of the service I HAVE TO add a web
reference to the service in the application references and the VS
guide that helps you doing that has to be able to access the service
itself to list it's methods and properties.
This is not possible because the service is not installed live
anywhere. So I cannot add the web reference and thus I cannot create
a web service object instance and use the web service methods and
properties in the app.

What is your developpment IDE ? With VS, just put the two projects in
the same solution and you will be able to generate the proxy class
without installing the web service.

If you can't do that. Install the web service somewhere (local IIS for
example if you have XP pro) and build the proxy class from the local
url.

Then you just have to change this url at runtime to address the actual
location of the service.
 
Thanks - as you see from my previous responses, these were two options I had
considered, but I didn't know if a better solution existed.

I'll try to do it one of these ways...

Best regards,
Johnny J.
 
Thanks - as you see from my previous responses, these were two options I had
considered, but I didn't know if a better solution existed.

I'll try to do it one of these ways...

Best regards,
Johnny J.
 
You seems to keep the idea that I don't understand you, but there is nothing
that you wrote that I did not understand.

What you don't understand is that the webservice need to be installed in
IIS. That is a job which mostly is done as it is not your own system by a
systemadmin.

When that is installed your program can reference to that. At debug or
release time in Visual Studio a special for Visual Studio made Internet
Information Server is used. The one which is then used is some derived from
Cassini, which itself is derived from the Personal Webserver from Windows
98.

Cor
 
You seems to keep the idea that I don't understand you, but there is nothing
that you wrote that I did not understand.

What you don't understand is that the webservice need to be installed in
IIS. That is a job which mostly is done as it is not your own system by a
systemadmin.

When that is installed your program can reference to that. At debug or
release time in Visual Studio a special for Visual Studio made Internet
Information Server is used. The one which is then used is some derived from
Cassini, which itself is derived from the Personal Webserver from Windows
98.

Cor
 
Cor,

The OP wants to create a WebService and a WebForms application to
access the WebService.

He will then send the WebService and WebForms application to other
people, who will install the WebService on their Web servers. Those
people will then want to run the WebForms application against the
WebService that is installed on their server. These other people are
perfectly capable of installing IIS and getting the WebService to run
on their servers.

Since the OP has no control over where the WebService is installed, he
needs a way for the other people to configure the WebForms application
to access the WebService running on their server. Presumably these
other people do not have Visual Studio.
 
Cor,

The OP wants to create a WebService and a WebForms application to
access the WebService.

He will then send the WebService and WebForms application to other
people, who will install the WebService on their Web servers. Those
people will then want to run the WebForms application against the
WebService that is installed on their server. These other people are
perfectly capable of installing IIS and getting the WebService to run
on their servers.

Since the OP has no control over where the WebService is installed, he
needs a way for the other people to configure the WebForms application
to access the WebService running on their server. Presumably these
other people do not have Visual Studio.
 
Back
Top