I used to call
NuGet.exe pack D:\Build\EasyHttp\src\EasyHttp\EasyHttp.csproj -OutputDirectory D:\Build\EasyHttp\Build\Release -BasePath D:\Build\EasyHttp -Verbose -Version 1.6.9.0 -Symbols -Properties Configuration=release
command to create my package.
After upgrade to NuGet 2.1 the command started to fail with
Could not find a part of the path 'D:\Build\EasyHttp\src\bin\release\'.
I noticed that for some reason -BasePath path was used to specify the base path to resolve paths from my .csproj file. The only value -BasePath worked right was to specify it to be D:\Build\EasyHttp\src\EasyHttp, but this breaks resolution of custom items in .nuspec file.
For more details of the error message (that was cryptic), see
http://teamcity.codebetter.com/viewLog.html?buildId=53642&buildTypeId=bt464&tab=buildLog
Comments: Not a bug
NuGet.exe pack D:\Build\EasyHttp\src\EasyHttp\EasyHttp.csproj -OutputDirectory D:\Build\EasyHttp\Build\Release -BasePath D:\Build\EasyHttp -Verbose -Version 1.6.9.0 -Symbols -Properties Configuration=release
command to create my package.
After upgrade to NuGet 2.1 the command started to fail with
Could not find a part of the path 'D:\Build\EasyHttp\src\bin\release\'.
I noticed that for some reason -BasePath path was used to specify the base path to resolve paths from my .csproj file. The only value -BasePath worked right was to specify it to be D:\Build\EasyHttp\src\EasyHttp, but this breaks resolution of custom items in .nuspec file.
For more details of the error message (that was cryptic), see
http://teamcity.codebetter.com/viewLog.html?buildId=53642&buildTypeId=bt464&tab=buildLog
Comments: Not a bug