locked
How to add dependency on VC110 to an 8.1 app built with VS2013

    Question

  • We are upgrading our app from 8.0 to 8.1 and are using a 3rd party dll that requires the VS2012 (VC110) redistributables. How can we declare a dependency on the VC110 runtime? The dll in question is added to our project as a content item that does not participate in the build, and our generated AppxManifest.xml only contains the following dependency:

      <Dependencies>
        <PackageDependency Name="Microsoft.VCLibs.120.00.Debug" MinVersion="12.0.21005.1" />
      </Dependencies>

    Thursday, January 23, 2014 12:01 AM

Answers

  • Hi Matthew,

    You'll need an updated version of the 3rd party DLL built with VS2013. The VC110 runtimes are not valid for a Windows 8.1 app, and there is no way to update a DLL short of rebuilding it.

    If your vendor cannot provide an updated DLL you'll have to stay with an 8.0 app.

    We are aware that this is a problem area but don't have a better solution.

    --Rob

    Thursday, January 23, 2014 12:09 AM
    Moderator

All replies

  • Hi Matthew,

    You'll need an updated version of the 3rd party DLL built with VS2013. The VC110 runtimes are not valid for a Windows 8.1 app, and there is no way to update a DLL short of rebuilding it.

    If your vendor cannot provide an updated DLL you'll have to stay with an 8.0 app.

    We are aware that this is a problem area but don't have a better solution.

    --Rob

    Thursday, January 23, 2014 12:09 AM
    Moderator
  • Would there be any issue (certification wise) with us adding msvcr110.dll and vccorlib110.dll to our app as content items so they are distributed alongside the 3rd party dll?
    Thursday, January 23, 2014 8:49 PM
  • I'd expect that including non-certifiable DLL as content would fail certification.

    --Rob

    Thursday, January 23, 2014 9:10 PM
    Moderator