Custom and defined a path. That said space in c:\Program Files\ caused it to fail. Worked when installed to c:\Nuget\. Might have worked as well if I chosen an %env….% defined path.There are two ways of doing it:
*.nuspec for a project within the solution.
Getting TC to invoke Nuget directly against a *.csproj file, and it will build the project, then the *.nupkg.
*.nuspec:XAct.Core.nuspec placed beside XAct.Core.csprojXAct.Core\XAct.Core\XAct.Core_Debug.nuspecXAct.Core\XAct.Corec:\Nuget\Nuget.exenuget that is running the build, and it's entry point is the *.csproj ([CHECKOUTDIR]\XAct.Core\XAct.Core\XAct.Core.csproj), it artificially sets the SolutionDir to the folder above it (eg: [CHECKOUTDIR]\XAct.Core\).
* As the SolutionDir is used by the *.csproj to import the Nuget.target file (<Import Project="$(SolutionDir)\.nuget\NuGet.targets" />), it is never found (one dir to deep):
'…The imported project “…\work\f5a3a0936d0bc94c\xact.core.nuget\NuGet.targets” was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk."
* Tried:
* Setting CommandLine to /Property:SolutionDir=<sln Dir>` didn't work (the COmmand Line is for the NuGet – not the MSBuild?)
* Benefits:
* Once working, it would be automated.
* Cons:
* Couldn't get it to work without a hack: had to put the .nuget directory in the the XAct.Core directory otherwise never found it.
* Much more difficult to get right.
http://bit.ly/sFBEk2 andhttp://bit.ly/rAXjKX