none
Deployment of libraries in Visual Studio 2012 RRS feed

  • Question

  • In Visual Studio 2008 it was possible to set the "Output File Folder" project property for libraries. But this is gone now in Visual Studio 2012?!

    It's not possible to deploy libraries to my device anymore?

    Friday, January 31, 2014 11:50 AM

Answers

  • "Output File Folder" is now "RemotePath" (some VS2012 update (at least in update 4)) under "Startup Project"/"Properties". Dependent referenced are deloyed there too. Not dependent-to-the-Startup-Project-libraries-which-are-consumed-via-Interop are not deployed and it sucks -> have to deploy them manually...
    • Marked as answer by Diddy Haring Tuesday, January 20, 2015 2:35 PM
    Tuesday, January 20, 2015 2:35 PM

All replies

  • AFAIK in VS2012 there is no option to Deploy additional files,as well as no option to configure deployment destination folder on the device.By default it is deployed to \temp directory.

    Please mark it as answer or vote as helpful if my reply helps.

    Regards,

    Prabu[eMVP]

    http://prabukumar.wordpress.com

    Friday, January 31, 2014 12:58 PM
  • The easiest way (call it workaround) to deploy a library (aka DLL) is via an executable.

    Add the desired library as dependency (reference) do an Application (EXE) Project. Dependant DLLs get deployed together with the application.

    Regards
    Michael


    MVP Windows Embedded

    Friday, January 31, 2014 10:05 PM
  • "Output File Folder" is now "RemotePath" (some VS2012 update (at least in update 4)) under "Startup Project"/"Properties". Dependent referenced are deloyed there too. Not dependent-to-the-Startup-Project-libraries-which-are-consumed-via-Interop are not deployed and it sucks -> have to deploy them manually...
    • Marked as answer by Diddy Haring Tuesday, January 20, 2015 2:35 PM
    Tuesday, January 20, 2015 2:35 PM