I have a Visual Studio 2013 class library project, a directory structure like this:
\MyClassLibraryProject \ExternalLibraries 3rdPartyLib.dll \bin \Debug \Release etc.
Inside the ExternalLibraries, I copied some third-party assemblies, which I then referenced in the project (Copy local = true). I will compile the project and in my Release directory, of course, I see MyClassLibraryProject.dll and third-party DLLs such as 3rdPartyLib.dll, etc. Still good.
Then I have another project (Console app - Azure webjob) from which I add a link to \ MyClassLibraryProject \ bin \ Release \ MyClassLibraryProject.dll (Copy local = true). It looks like this:
\MyWebjob \bin \Debug MyWebJob.exe MyClassLibraryProject.dll 3rdPartyLib.dll
So, as you can see, when I added a link to MyClassLibraryProject.dll (with Copy local = true), it also copied its dependent assembly 3rdPartyLib.dll. Okay bye.
However, when publishing a webjob project for Azure (right-click Project, Publish ...). 3PartyLib.dll is not deployed. As a result, the webjobs toolbar complains that it cannot be found and, of course, the website is not running.
Is this user error or something else?
source share