I created a Hello World webservice-published it - how to call it?

  • Thread starter Thread starter BC
  • Start date Start date
B

BC

Hello,

I just created a Hello World webservice in VB2005 (this is my first
webservice ever). I ran it in debug mode and the page that came up said
Hello World and said to change the webservice namespace from tempuri.org to
something else so that the xml file could be created. I did that. Then it
said to make a web reference (say what?) The only web reference I was able
to make was to the local solution: Local Host. Then in the build I
selected publish. The project was copied to a virtual directory on my IIS
webserver (Service1.asmx and related files).

When I tried to call it from Internet Explorer I got an error message. I
typed something like

myVirtualDir/mywebservice/Service1.asmx

This brought up an error page and suggested that I create a custom errors
tag in web.config and set it to off to get a better error message. This is
getting a little complex for me. So what is the correct way to deploy/call
my new webservice?

Thanks,
BC
 
Hello,

I just created a Hello World webservice in VB2005 (this is my first
webservice ever). I ran it in debug mode and the page that came up said
Hello World and said to change the webservice namespace from tempuri.org to
something else so that the xml file could be created. I did that. Then it
said to make a web reference (say what?) The only web reference I was able
to make was to the local solution: Local Host. Then in the build I
selected publish. The project was copied to a virtual directory on my IIS
webserver (Service1.asmx and related files).

When I tried to call it from Internet Explorer I got an error message. I
typed something like

myVirtualDir/mywebservice/Service1.asmx

This brought up an error page and suggested that I create a custom errors
tag in web.config and set it to off to get a better error message. This is
getting a little complex for me. So what is the correct way to deploy/call
my new webservice?

Thanks,
BC
Click to expand...

Have you set the web service as a .Net app in IIS?

Thanks,

Seth Rowe
 
The only thing I have done so far is to publish the webservice to IIS. I
look at IIS virtual dirs and there are the files (the .asmx file ...). I
have not done anyting (anything else regarding this webservice) in IIS. How
do I set my webservice as a .Net app in IIS?
 
The only thing I have done so far is to publish the webservice to IIS. I
look at IIS virtual dirs and there are the files (the .asmx file ...). I
have not done anyting (anything else regarding this webservice) in IIS. How
do I set my webservice as a .Net app in IIS?
Click to expand...

I have not done this in a while, and do not currently do any IIS admin
stuff, so my advice could be off.

With that said, I believe you right click on the virtual directory and
go to properties. One of the tabs should be called something like
"ASP.NET", you need to open that tab. One of the drop downs should
have the target framework version, which by default is set to 1.1.
This is the property you need to set to 2.0 (if you wrote this
with .NET 2.0 (VB 2005)).

Thanks,

Seth Rowe [MVP]
 
Thanks. In my virtual directory/properties dialog I don't see an ASP.Net tab
(and yes, I created this webservice in VB2005 - .Net framework 2.0). But in
the "Directory" tab there is a Create Button to the right of a textbox titled
Application Name: which is currently disabled (the textbox, not the button).
And inside the textbox it says Default Application - grayed out. I am
tempted to click on the Create button, but this is our production webserver,
and I don't want to interfere with anything. You think there would be any
harm in clicking The Button?
 
Thanks.  In my virtual directory/properties dialog I don't see an ASP.Net tab
(and yes, I created this webservice in VB2005 - .Net framework 2.0).   But in
the "Directory" tab there is a Create Button to the right of a textbox titled
Application Name:  which is currently disabled (the textbox, not the button).
 And inside the textbox it says Default Application - grayed out.   I am
tempted to click on the Create button, but this is our production webserver,
and I don't want to interfere with anything.  You think there would be any
harm in clicking The Button?






- Show quoted text -
Click to expand...

I'm not the person to ask, I'm not a IIS expert by any means. Who is
your web server admin? They should have the necessary knowledge on
setting up .NET apps. If not you might post to a IIS newsgroup, though
I'm not sure what the newsgroup name or link is.

Thanks,

Seth Rowe [MVP]
 
Thanks. I was thinking this might be a web related question, so yes I will
post to an IIS group.

As for the admin, there isn't really an admin. I am the backend guy and
make client apps for inhouse workstations/users. We have a web guy, in
another state, who is the front end guy. I did ask him since he does most of
the stuff on IIS. He hasn't gotten back to me yet. But I am sort of free to
do as I please on our IIS - thus, I want to proceed carefully. I currently
use IIS mostly for app deployment with Click Once and an aspx page where the
inhouse users can download the apps. The webservice thing is mainly for
taking my backend stuff to the next level.
 
To put a service that you created in Visual Studio at a site run IIS , all I
do I do is put the associated dll in the bin folder in the root directory
and put the asmx file anywhere else that is not the bin directory. At least
that is what I recall doing. I haven't done one in several months.
 
Back
Top