locked
Deploy Version Issue? RRS feed

  • Question

  • Note:   I seem to have solved the problem - I was attempting to deploy it into a directory one level below the RDS root.  I still have a question - it overwrites things like NXTBrick. .. .proxy.dll, etc.  where I have not modified them.   Shouldn't it use the copy in the existing RDS (where such is installed on the target node)?   Does this affect the assembly strong name?
       --Don


    I've generated a DssDeploy package (successfully, I think).   I can successfully install it on a target machine.   However, when I try to invoke it using DssHost,  I get a Manifest Loader error.   It claims that I have a version problem with NxtBrick.Y2007.M07.Proxy   showing a version of 0.0.0.0.   

    On both machines, I have a fresh install of MRDS (CTP2).   Obviously, there is something going on here I don't understand. 

    Also, on both machines, I've disabled authentication (can't get that to work either).  

    I'm not sure where to look for a solution - advice appreciated.

      --Don

    ____________________
    The response from the CLI is:

    **  Error creating service. Service type:http://schemas.tempuri.org/2008/07/swee
    pultrasound.html [08/30/2008 14:09:05][http://feynman:50000/constructor/1974c75f
    -27fa-4e55-adc2-974b88624468]
    *** Manifest Loader: Creating service failed: http://schemas.tempuri.org/2008/07
    /sweepultrasound.html.
    Reason: Exception has been thrown by the target of an invocation.    System.Refl
    ection.TargetInvocationException: Exception has been thrown by the target of an
    invocation. ---> System.IO.FileLoadException: Could not load file or assembly 'N
    xtBrick.Y2007.M07.Proxy, Version=0.0.0.0, Culture=neutral, PublicKeyToken=de5576
    3756f81ddf' or one of its dependencies. The located assembly's manifest definiti
    on does not match the assembly reference. (Exception from HRESULT: 0x80131040)
        File name: 'NxtBrick.Y2007.M07.Proxy, Version=0.0.0.0, Culture=neutral, Publ
    icKeyToken=de55763756f81ddf'
           at sweepUltrasound.sweepUltrasoundService..ctor(DsspServiceCreationPort c
    reationPort)

    Saturday, August 30, 2008 7:16 PM

Answers

  • Depending on how you create the DssDeploy package, it can include all of the dependent DLLs. If you have recompiled any of the MRDS services on your machine before you make the package, it is possible to include DLLs that have a new version. This can happen inadvertently if you open one of the samples and then run it in the debugger because that re-compiles the proxy.

     

    You can see the version information of a DLL in the Properties if you right-click on it in Windows Explorer and look in the Details tab.

     

    Trevor

     

     

     

     

    Wednesday, September 3, 2008 12:00 AM