Fix typo in build.cmd
Replace individual parameters with wildcard

    It's not that we ever want to pass more than ten arguments; it's about
    the fact that we'd like to be able to pass arguments like this:

        .\build.cmd /p:OutDir='D:\test\'

    Using individual arguments, MSBuild is called like this:

        MSBuild.exe /p:OutDir D:\test\

    That's because the equal sign is considered a separator in batch files.
Fix whitespace
Stop excluding non-library when packaging

We currently exclude files that come from dependencies. This is great
for library files as this prevents dependencies from being packaged.

However, this doesn't work for cases where folks also add binaries
to non-lib locations, for example the tools directory. In those cases,
we don't want to exclude files that are coming from dependencies and
instead assume the developer did this intentional.

This fixes #14.
Don't include files that come from indirect NuGet dependencies

This fixes issue #10 which causes the following scenario to not work.
Consider this project structure:

  A.csproj => ANuGetPackage
  A.nuproj => A.csproj
  B.csproj => A.csproj
  B.nuproj => B.csproj, A.nuproj

B.nupkg should not contain assemblies from ANuGetPackage but it does.
The root cause is that we don't use the closure of NuGet packages to
exclude files where we should.

The current behavior will now also cause the package to depend on the
closure of packages, as opposed to only the direct dependencies. We
should probably fix that.
Don't depend on closure of NuGet packages

We need to gather the closure in order to not package files that come
from direct or indirect NuGet dependencies. However, we don't want the
resulting .nupkg file to depend on the closure.
Merge branch 'issue10' of https://github.com/terrajobst/nuproj

added sample