"Stan" <nospam@yahoo.com> wrote in message
news:OD5aliTWEHA.3596@tk2msftngp13.phx.gbl...
> I drop and re-register a serviced component every time there is a new
method
> or a change in the parameters of an existing method.
>
> I found out that even if I keep the old version of the component in COM+
and
> simply replace the assembly, it still works. I don't use COM+ clients, so
> there is no interop involved in calling the component. New methods are not
> visible in COM+ snap-in but .NET clients seems don't have problems calling
> it (since they rely on metadata).
>
> Is it ok not to reinstall the component in COM+? What ramifications can it
> have?
>
> Thanks,
>
> -Stan
>
>

"Ice" <ice@nospam.com> wrote in message
news:OkMcYxSXEHA.1164@tk2msftngp13.phx.gbl...
> Are they installed as server or library application.
> ice
> "Stan" <nospam@yahoo.com> wrote in message
> news:OD5aliTWEHA.3596@tk2msftngp13.phx.gbl...
> > I drop and re-register a serviced component every time there is a new
> method
> > or a change in the parameters of an existing method.
> >
> > I found out that even if I keep the old version of the component in COM+
> and
> > simply replace the assembly, it still works. I don't use COM+ clients,
so
> > there is no interop involved in calling the component. New methods are
not
> > visible in COM+ snap-in but .NET clients seems don't have problems
calling
> > it (since they rely on metadata).
> >
> > Is it ok not to reinstall the component in COM+? What ramifications can
it
> > have?
> >
> > Thanks,
> >
> > -Stan
> >
> >
>
>