We´re creating an Octopack of .Net framework web app, with msbuild and octopack, but it’s failing due to “too long path error”. The error it’s thrown when msbuild starts to create the octopac, the error came from the nuget.exe inside the octopack nuget package, we’re using last octopack nuget version.
Thanks for your response, we’ve check it. But we also include in the octopack other files a part from the binaries of the web app taking advantage of the nuspec “<file src=” mechanism .
How can we include files that are not binaries one?
With a script copying the files to the publish build folder? Is there something similar of the nuspec mechanism but for the Octopus cli to avoid having to copy the files with scripts?
It looks promisings, just a final question. I’ve done some runs with the --include parameter but if say "–include .\views* it’s copying the content of the folder to the root of nuget package. What I would like it’s in the nuget has the folder views with its content. Do you know how can I do it?
It would be the equivalent of the target in the nuspec file when creating a octopack from the msbuild
Hello @donny.bell ,
Finally we will do an script to move the files/folders we need before creating the octopack.
But just to let you know, We’re using the octo cli to creare the package in nupkg format. Executing the same command just changing the format, the resultant package it’s completely different. I would expect just changing the format the content of the output package to be the same.
