Re: ActivationOption.Server doesent work, but libary does

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

From: Steve Drake (Steve_at__NOSPAM_.Drakey.co.uk)
Date: 06/16/04

  • Next message: Ice: "Re: ActivationOption.Server doesent work, but libary does" 
    Date: Wed, 16 Jun 2004 17:36:35 +0100

    I've tried it in the GAC still doesn't work (I would prefer not to have it
    in the GAC),

    I X posted to ASP.NET as I am running the component from ASP.NET and I know
    from experience that this throws over COM+ issues into the MIX, but... I
    forget to mention that in my original post.

    Steve

    "Ice" <ice@nospam.com> wrote in message
    news:udgRWz7UEHA.1036@TK2MSFTNGP12.phx.gbl...
    > is it in the GAC?
    >
    > pls don't crosspost.
    >
    > ice
    > "Steve Drake" <Steve@_NOSPAM_.Drakey.co.uk> wrote in message
    > news:OtoieB6UEHA.1652@TK2MSFTNGP09.phx.gbl...
    > > Already done.
    > >
    > > Cheers
    > >
    > > Steve
    > >
    > >
    > > "José Miguel Torres" <jtorres_diaz~~ARROBA~~terra.es> wrote in message
    > > news:#$DBUB5UEHA.1652@TK2MSFTNGP09.phx.gbl...
    > > > make safe assembly name for your component using sn -k
    > > nameassembly.snk....
    > > >
    > > >
    > > > regards
    > > >
    > > >
    > > > --
    > > > José Miguel Torres
    > > > jtorres_diaz~~ARROBA~~terra.es
    > > > http://jmtorres.blogspot.com
    > > > "Steve Drake" <Steve@_NOSPAM_.Drakey.co.uk> escribió en el mensaje
    > > > news:#qt2P34UEHA.3420@TK2MSFTNGP12.phx.gbl...
    > > > > All,
    > > > >
    > > > > I have a servicedcomponet that works fine if its activated as
    library
    > > app,
    > > > > but doesn't work if its activated as a server component.
    > > > >
    > > > > I get the following error :
    > > > >
    > > > > System.Runtime.Serialization.SerializationException: Cannot find the
    > > > > assembly Project.Common, Version=6.0.1628.18135, Culture=neutral,
    > > > > PublicKeyToken=0b8a1eb77127c657.
    > > > >
    > > > > I have lets .NET register the componet and I have also tried :
    > > > >
    > > > > regsvcs <DLL> /appdir:<PATH>
    > > > >
    > > > > The DLL mentioned is in the correct folder.
    > > > >
    > > > > Cheers
    > > > >
    > > > > Steve
    > > > >
    > > > >
    > > >
    > > >
    > >
    > >
    >
    >

  • Next message: Ice: "Re: ActivationOption.Server doesent work, but libary does"

    Relevant Pages

    • Re: ActivationOption.Server doesent work, but libary does
      ... I do have a .NET server application that does not belong to the GAC, ... Steve ... > COM+ server applications must have the constituent assemblies in the GAC. ...
      (microsoft.public.dotnet.framework.component_services)
    • Re: CLR was running a version of my dll that didnt exist!?!?
      ... > (the only way to run a COM+ server app). ... > uninstall it from both the gac and com+ (doesn't show up in the GAC ... > and the com+ app is gone) we then install foo.dll version 1.0.1 into the ... Is it caching the JIT code somewhere that ...
      (microsoft.public.dotnet.framework.clr)
    • Re: To GAC or not to GAC, that is the question
      ... Well, theoretically, if you updated your DLL, you would want it to available ... >> Since you will have multiple applications using the same DLL, the GAC ... Having multiple copiues of a DLL ... Would you want to run the risk of an update of App A causing ...
      (microsoft.public.dotnet.general)
    • CLR was running a version of my dll that didnt exist!?!?
      ... OK, we have a .NET dll hosted in COM+ running as a queued, pooled ... component - I say this as an explanation of why my assemlies are in the GAC ... (the only way to run a COM+ server app). ... and the com+ app is gone) we then install foo.dll version 1.0.1 into the ...
      (microsoft.public.dotnet.framework.clr)
    • Re: How can I use a dll with several programs?
      ... Using the GAC has it`s advantages however my statement is that i would not ... it costs more complexity again to even deploy your app or it costs essential ... that you do not get with private assemblies. ... leads to a set of well-known problems collectively called "DLL Hell." ...
      (microsoft.public.dotnet.languages.vb)