Chris/0

This is something I've tackled in #183.

@paul-michalik `sam build` calls `dotnet lambda package` under the hood, so it will read "aws-lambda-tools-defaults.json" files in the project directory.

Ah, I think I see the confusion. It does pick up that file in those locations with many of its settings, as I've confirmed from testing, but it doesn't read...

Unless the architecture has changed since I last looked, `sam build` calls `dotnet lambda package` under the hood, traversing each `CodeUri` in the SAM template. I recall from #122 that...

>I'll see if I can cook up an example. Great! I'm looking forward to seeing how that looks.

Yup, I'm running with this. I'll have it cleaned up and working for commit in… probably a couple of hours. ETA: Or one hour, whenever.

> There are a few tests failing because […] Hm, can you let me know which ones? I can't recreate. Though I don't have a scratch AWS account in which...

> With 2017 we will need to down version of MSBuild.Build to version 15.* which targets .NET Framework 4.6 which is the minimum for VS 2017. I have tests now...

>Hm, can you let me know which ones? I can't recreate. Yes, I can, it's `CreatePackageTests`. There's something I don't understand happening because I can get `CreatePackageTests` to pass when...

_"If only we had a way to run `dotnet` commands from here in the tool," he thought, failing to realize._ The target framework determination now exfiltrates MSBuild properties (`TargetFramework` and/or...