Strong Name Assembly

From: Chris (123_at_123.com)
Date: 11/20/05

  • Next message: MoF: "Re: Server.CreateObject("Scripting.FileSystemObject")" 
    Date: Sun, 20 Nov 2005 17:44:45 -0000

    I have a strong named assembly. It installs fine on my XP Pro Machine via
    the .net configuration tool. When I use the same tool to install it on a
    W2003 machine it says it isn't strongly named.
    As I don't have vs.net. Ihave been compliling my vb file as a module and
    then using al.exe to sign it with a strong name. It seems to work on my
    machine. When I copy the dll to the 2003 machine it doesn't. Does it need
    any additional files than the dll. Also the W2003 machine is .net v2 whereas
    my machine is .net v1. The 2003 machine is a brand new installation of 2003,
    which I don't know much about other than it is 'locked down'. Could there be
    some kind of permissions issue?

  • Next message: MoF: "Re: Server.CreateObject("Scripting.FileSystemObject")"

    Relevant Pages

    • Strong Name Assembly
      ... It installs fine on my XP Pro Machine via ... the .net configuration tool. ... When I copy the dll to the 2003 machine it doesn't. ...
      (microsoft.public.dotnet.security)
    • Re: Strong Name Assemby
      ... It installs fine on my XP Pro Machine ... > via the .net configuration tool. ... That way you do not have to compile the code as a module, ... When I copy the dll to the 2003 machine it doesn't. ...
      (microsoft.public.dotnet.framework)
    • Re: Movie Maker wont start
      ... I renamed all of the dll files you suggested and then ... >something is dying when dshow goes to enumerate the ... FXLibrary (This installs FXLibrary.dll) ...
      (microsoft.public.windowsxp.moviemaker)
    • Re: MFC DLL at Application Folder Saves Memory As Well?
      ... > do the two applications share memory and I can save memory? ... Suppose the user installs ... application A that drops the DLL into system32. ...
      (microsoft.public.vc.language)
    • Re: Error 50002
      ... installing Word US installs a, I presume, shared dll, that is newer than ... the one Word FR installs? ... > SP installed or not does no matter. ... > In each scenario, the Win installation is a fresh one. ...
      (microsoft.public.vb.com)