Making nuget install binaries to ${project}\libs

[mshafer1]

Specifying the destination of the files on install so that a pre-build step can become something like:
$(ProjectDir)libs\AutoImplement
without any extra work.

[haven1433]

Unfortunately, this is a breaking change... if this was submitted as part of 1.1.0, anyone who upgrades to 1.1.0 from 1.0.1 will no longer be able to find the DLL without changing their applications.

Breaking changes should wait until we're ready for version 2.0.0. So either this pull request needs to wait for that, or be closed and changed into an issue as a desired feature for version 2.0.0.

[haven1433]

is content\libs the best possible place for this? I would think that content\tools might be more appropriate. Libs/lib is usually reserved for libraries that you want to reference (such as the nuget target="lib" used for System.Delegation). "Tools" is probably a better name for something called as a pre-build step that isn't actually referenced by the project.

[mshafer1]

I only selected libs because that is the path that is currently suggested in the wiki. I agree that tools makes more sense.

[haven1433]

Good point. While updating the wiki, I went ahead and updated that path based on the current expected install scenario. I can update it again once this gets merged in.

[mshafer1]

Unfortunately, this is a breaking change... if this was submitted as part of 1.1.0, anyone who upgrades to 1.1.0 from 1.0.1 will no longer be able to find the DLL without changing their applications.

So, current behavior is installing the nuget puts the exe under the nuget root (which is typically under the users home directory, but can be customized even on a per solution basis), and the dll's that need to be depended on under lib (which causes them to be added to the project as resources).

I would not expect this to be a breaking change as people should not be installing a Nuget to a project, but then using a global (system) path to call the exe. (Albeit, it is different than the current behavior and I can understand waiting for 2.0 to accept the merge).

[haven1433]

So, current behavior is installing the nuget puts the exe under the nuget root (which is typically under the users home directory, but can be customized even on a per solution basis), and the dll's that need to be depended on under lib (which causes them to be added to the project as resources).

I haven't done anything to change the default behavior on my machine. "Manage Nuget Packages" through VisualStudio installed the nugets into a folder called "packages" inside my solution directory. This is reflected by the $(SolutionDir)packages path used in the wiki.

Not sure why the default nuget install location is different from your machine to mine, but it does reinforce that (1) this change is required, to help provide consistency in how a project using AutoImplement finds the exe, and (2) this is a breaking change that needs to wait for a major version bump.