Non-project references and Version Number

Oct 29, 2014 at 5:26 PM
Danny,
I have tried version 2.6.0 but it's not pulling the "Copy Local" Assembly references.
Also, is it possible to provide a command argument to enable 4-part version number?

For now, I'll have to use my customized version.

Thanks!

Richard
Coordinator
Nov 2, 2014 at 6:33 PM
Edited Nov 2, 2014 at 6:34 PM
Hi Richard,

Please see the example in the source code for how to add non-NuGet assembly references.
In a nutshell, you need to add a folder named "lib" under the NuGet project, then copy or link (preferably the latter) assemblies (and pdbs, xmls) under it.

Regarding the 4-part version number, I'll see if I can enable it without breaking the default 3-part version numbers, perhaps only use it when not-0.

Regards,
Danny.
Nov 4, 2014 at 4:36 AM
Danny,
My objective is to get the lib information from the target project without adding anything to the NuGet project, as in the code I have provided. So far, it works well for me.


Richard.
Coordinator
Nov 4, 2014 at 7:35 PM
I understood your design, however, I that approach seemed too risky to me, as you may end up packaging MS DLLs or Native (x86/x86) DLLs. I prefered an explicit include in package approach over the implicit one.
Marked as answer by dannyvarod on 11/4/2014 at 11:35 AM
Coordinator
Dec 16, 2014 at 8:27 PM
4-part version numbers should be working now.