Latest post Mon, Oct 22 2018 6:24 PM by Rich Laws. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • Sat, Sep 8 2018 11:01 PM

    • Rich Laws
    • Not Ranked
    • Joined on Wed, Oct 17 2012
    • Posts 65
    • Points 615

    Possible deployment issue with an AMT3 component?

    Hello,

    I built a deployment project for our application (Visual Studio 2017) that included the AMT3 (mediaprocessor-win-vc12-x64-4.4.18.10034) components and a merge module for VC 2013 version (120) c++ run time support.  (AMT project platform toolset is VS2013)

    After installing on a virgin system (2012R2), the application failed to run because of a missing component.  Using procmon, I traced this to one of the AMT3 dlls (MXFviaAAF.dll) attempting to load the VS2012 c++ runtime library. 

    To resolve, I added msvcr110 and msvcp110 merge module components to the deployment project and the application now loads and runs successfully. 

    Can I ask the developers to verify if this is the case?  This may or may not be considered an issue but I wanted to call it to everyone's attention.

    Rich

     

  • Mon, Oct 22 2018 6:24 PM In reply to

    • Rich Laws
    • Not Ranked
    • Joined on Wed, Oct 17 2012
    • Posts 65
    • Points 615

    Re: Possible deployment issue with an AMT3 component?

    Just a follow up note (FYI - no action required):

    These DLLs in the distribution require the VS2012 c++ runtime libraries:

        AAFCOAPI.dll, MXFviaAAF.dll, AMAUtilLib20.dll, Avicuuc51.dll

    All other DLLs in the distribution require the VS2013 c++ libraries.  As noted, I've simply added the VS2012 merge modules (msvcr110 and msvcp110)  to my deployment package to resolve the issue. 

Page 1 of 1 (2 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller