Web Service Deployment Issues

I have a Web Service developed using C# and the .NET framework v1.1.

When I access the DLL on the localhost, using the URL

http://localhost/Folder/bin/MyService.dll

it works fine. However, when I x-copy deploy the DLL and its web.config
(authorization allow *) to a remote server and set all permissions for
the account ASPNET (the local ASPNET account), I have problems
accessing the same url remotely like:

http://remoteserver/Folder/bin/MyService.dll

Any pointers?

dale0973
Thu Feb 02 12:26:08 CST 2006

Shouldn't you be using http://remoteserver/folder/myservice.asmx to access
your webservice?
--
Dale Preston
MCAD C#
MCSE, MCDBA


"Sathyaish" wrote:

> I have a Web Service developed using C# and the .NET framework v1.1.
>
> When I access the DLL on the localhost, using the URL
>
> http://localhost/Folder/bin/MyService.dll
>
> it works fine. However, when I x-copy deploy the DLL and its web.config
> (authorization allow *) to a remote server and set all permissions for
> the account ASPNET (the local ASPNET account), I have problems
> accessing the same url remotely like:
>
> http://remoteserver/Folder/bin/MyService.dll
>
> Any pointers?
>
>

Sathyaish
Thu Feb 02 14:03:14 CST 2006

Thanks. That was an obvious bit I forgot. I am sure I knew that
somewhere in my brain but just totally brain farted on it.

Now, what are the other files that one deploys when deploying a web
service? The asmx, the dll and what? I am sure you don't deploy the .cs
file?

pbromberg
Thu Feb 02 14:37:27 CST 2006

Sathyaish,
Normaill you would deploy the built assembly (dll) into the /bin folder,
the .asmx file, and the web.config and global.asax files.

Ensure that the debug setting in web.config is set to "false" and that you
have built the service in Release mode build configuration.
It also needs to be an IIS Application.

Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




"Sathyaish" wrote:

> Thanks. That was an obvious bit I forgot. I am sure I knew that
> somewhere in my brain but just totally brain farted on it.
>
> Now, what are the other files that one deploys when deploying a web
> service? The asmx, the dll and what? I am sure you don't deploy the .cs
> file?
>
>

Sathyaish
Thu Feb 02 15:32:41 CST 2006

Thanks, Peter. It seems I'd just not cared to copy the asmx probably
because I didn't know or probably knew but had forgotten. I'd copied
the web.config though and set the correct authorization, customErrors
(@mode=RemoteOnly, which is also the default) etc.

Good thing you reminded me about the debug switch. I know that also but
I have forgotten the syntax for that. It was something like:

<somethng here debug="false" />

that helped not to pop up the "dude! wanna debug? What're you gonna
use?". What was the syntax, please?

NoSpamMgbworld
Fri Feb 03 09:09:46 CST 2006

You have to deploy:

1. DLL (/bin)
2. ASMX

No code files.

NOTE that this can technically just be the DLL in 2.0, if you compile using
the command line tools (prep for no file deploy, or whatever it is called).

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************


"Sathyaish" wrote:

> Thanks. That was an obvious bit I forgot. I am sure I knew that
> somewhere in my brain but just totally brain farted on it.
>
> Now, what are the other files that one deploys when deploying a web
> service? The asmx, the dll and what? I am sure you don't deploy the .cs
> file?
>
>