Common Component Deployment Options

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Mansoor Siddiqui (MansoorSiddiqui_at_discussions.microsoft.com)
Date: 02/10/05 

Date: Thu, 10 Feb 2005 06:51:04 -0800

Hi all,

I have a common component that will be used from many applications in my
organization. There are different ways to host that component, such as:

(1) As COM+ application on a server
(2) As a shared assembly in GAC on every machine
(3) As a remoting component hosted in IIS
(4) As a private assembly in each and every client application's bin/root
directory
(5) Any other option ?

Each of the above has its own pros and cons but considering my requirements
where that component can be called from any application across the network, I
am having hard time determining what to do. I myself am inclined towards the
options of having that common component as a .NET remoting component hosted
in IIS and have clients call it over HTTP Binary!

So gurus pls help and suggest what is the best way to deploy such a common
component? Please note that a "less maintenance" and "high scalability"
solutions are always preferred.

Thanks,
Manny

Relevant Pages

  • RE: Common Component Deployment Options
    ... considered having your applications check for component updates on startup ... > As a private assembly in each and every client application's bin/root ... > options of having that common component as a .NET remoting component hosted ... > in IIS and have clients call it over HTTP Binary! ...
    (microsoft.public.dotnet.framework.performance)
  • Common Component Deployment Options
    ... I have a common component that will be used from many applications in my ... There are different ways to host that component, ... As a remoting component hosted in IIS ... As a private assembly in each and every client application's bin/root ...
    (microsoft.public.dotnet.framework.remoting)
  • Common Component Deployment Options
    ... I have a common component that will be used from many applications in my ... There are different ways to host that component, ... As a remoting component hosted in IIS ... As a private assembly in each and every client application's bin/root ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: how to configure host headers for 3 IIS machines ?
    ... The CS-Host field is sent by the client. ... If the server is configured with host headers only, ... Kristofer Gafvert - IIS MVP ...
    (microsoft.public.inetserver.iis)
  • Re: cs-host, host header and destination
    ... Host Header information was>www.microsoft.com. ... The webserver does not care ... Header for www.microsoft.com on this server, the>client got back a page! ... and I was wondering where and how that was set in IIS. ...
    (microsoft.public.inetserver.iis)