Packing stops looking for dlls if it doesnt find 1 row in the dna config

[jordanov1991]

The packing doesn't break but instead packs the DLLs it finds up until the 1 it doesn't find in the DNA config. All refs after the missing one are not added to the package.

[govert]

Do you think it should rather fail the build?

[jordanov1991]

I would expect it to fail the build with an error if it can't find all the dlls. It's presumed they're all needed. Barring that at least pack the dlls remaining in the config after the one that wasn't found. Currently say you have 25 dlls in the DNA config. 6th one is missing, so you pack first 5 and are missing 75% of the build functionality.

[govert]

@Sergey-Vlasov Maybe we can revisit the packing task a bit:

• it should fail the build if there are files it can't resolve
• the logging should go through the build logging, not just console output
• anything else to make it behave better now that it is a build task?

[Sergey-Vlasov]

I've added <ExcelAddInInclude>missing.dll</ExcelAddInInclude> to a . csproj and the build failed with:

MSBUILD : PackExcelAddIn error DNA736618949: ~~> ERROR: Reference with Path: missing.dll and Name: NOT FOUND.

Also directly added <Reference Path="missing.dll" Pack="true" /> to a .dna and the build failed the same.

Can you please provide an example project demonstrating successful build with a missing dll?