Deploy multiple .Net web services?

17 Jul 2006 5:46 PM

Fan

Dear all,

Now I am experiencing problems in deploying .Net web services to
production servers. We have multiple web services which share some of
the common libraries (.Net assemblies and .Net COM objects). These
common assemblies are put in "Common" directory. The structure looks
like:

c:\inetpub\wwwroot
                        -------- WS1
                        -------- WS2
                        -------- WS3
                        -------- Common

My question is how we can deploy this structure to the production
server efficiently. Can we build one set up (or windows installer)
program to maintain the same structure? Do we have to put the common
dlls into GAS in order to share them? Also, it is better that the
setup program could call "regasm" to register the .Net COM dlls
automatically. Is this feasible?

Thanks very much.

Fan

24 Sep 2006 1:47 AM

Cowboy (Gregory A. Beamer)

GAC is better if you are going to use the same libaries from multiple
projects. It is a one time install and makes things simple. I have heard
(not confirmed) instances when GACing a COM wrapper causes issues, however,
so test the solution.

If this is not an option, you can deploy the same dlls with each service.
While this takes up more disk space, it is not a bad option otherwise. It
also gives you the ability to update the libraries independently, although
you should try not to do that.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com/

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

Show quote

"Fan" <fyan***@gmail.com> wrote in message
news:1153158367.122258.206640@h48g2000cwc.googlegroups.com...
> Dear all,
>
> Now I am experiencing problems in deploying .Net web services to
> production servers. We have multiple web services which share some of
> the common libraries (.Net assemblies and .Net COM objects). These
> common assemblies are put in "Common" directory. The structure looks
> like:
>
>
> c:\inetpub\wwwroot
>                        -------- WS1
>                        -------- WS2
>                        -------- WS3
>                        -------- Common
>
>
> My question is how we can deploy this structure to the production
> server efficiently. Can we build one set up (or windows installer)
> program to maintain the same structure? Do we have to put the common
> dlls into GAS in order to share them? Also, it is better that the
> setup program could call "regasm" to register the .Net COM dlls
> automatically. Is this feasible?
>
>
> Thanks very much.
>
>
> Fan
>