Wow, it works, thank you!
I did it just as you suggested: by packing the main dna file and linking the 'outside' one from it.
The only downside I noticed is that I need to recreate the outside dna in the file system relatively to bin\Debug (or bin\Release) directory.
Given I want to eventually have such tree:
%appdata%/
|---------Microsoft
|---------|---------Addins
|---------|---------|---------PackedAddin.xll
|---------MyAddin
|---------|---------Studio
|---------|---------|---------lib
|---------|---------|---------|---------Newtonsoft.dll
|---------|---------outside.dna
My dna files looks like below:
packed.dna:
<ExternalLibrary Path="..\..\MyAddin\Studio\outside.dna"/>
outside.dna:
<ExternalLibrary Path="lib\Newtonsoft.Json.dll" />
but during the build, the DnaPackageTool is trying to localize the '..\..\MyAddin\Studio\outside.dna' from \bin\Debug context - so I need to create this file precisely in this context, which brings the necessity of moving it back and forth in case of modifying the target path. Do you have any suggestions on how could I improve this process? Or is that's really the only way I can do this?
Thank you very much!
Wojciech