Write-NuGetPackage uses the project directory as intermediary directory.
If the project with id "MyLib" defines own MyLib.targets or MyLib.props files they are overwritten and deleted with the internal generated MyLib.targets and MyLib.props files.
Also, there is no way to specify destination for the generated .nupkg package.
It would be great if the Write-NuGetPackage supported -DestinationPath, -IntermediaryPath and -LeaveIntermediaryFiles switches
-DestinationPath for .nupkg output directory (default to project directory)
-IntermediaryPath for debugging generated files (default to some temporary directory)
-LeaveIntermediaryFiles for leaving generated files. Already exists -NoClean.
Any special reason for using the project directory?
Write-NuGetPackage uses the project directory as intermediary directory.
If the project with id "MyLib" defines own MyLib.targets or MyLib.props files they are overwritten and deleted with the internal generated MyLib.targets and MyLib.props files. Also, there is no way to specify destination for the generated .nupkg package.
It would be great if the Write-NuGetPackage supported -DestinationPath, -IntermediaryPath and -LeaveIntermediaryFiles switches -DestinationPath for .nupkg output directory (default to project directory) -IntermediaryPath for debugging generated files (default to some temporary directory)
-LeaveIntermediaryFiles for leaving generated files.Already exists -NoClean.Any special reason for using the project directory?