We’ve got a Shared folder with power shell scripts that are referenced from our Deploy.ps1. If we set the file as ‘Content’ & ‘Do not copy’ IF it’s a linked file it’s not included in the package.
I’ve seen there’s work done to get this to work but it’s not working for us! We’re using 2.0.26
Our folder structure looks like this:
@@@
\Solutions\*.sln
\Solutions\.Octopack\OctoPack.Tasks & dll…etc.
\Solutions\Shared\
\IIS\ (referencing the ps scripts in ‘shared’ plus a local ‘Deploy.ps1’
@@@
I’m not sure if that’s significant.
Let me know if you need any further info.
Cheers,
Graeme.
Actually…
The shared folder are in a folder called .Acme in the solution folder, and files starting with a . are ignored by nuget.exe by default…
I’ve hacked the 'CreateOctopackPackage.cs to pass througth the -NoDefuatExcludes command line param to include the file… but this is a quick and dirty fix.
Cheers,
Graeme.
I’ve added a property to the octopack task and updated the targets file, seems like a better solution.
@@@
<CreateOctoPackPackage
NuSpecFileName="$(OctoPackNuSpecFileName)“
ContentFiles=”@(Content)“
OutDir=”$(OutDir)“
ProjectDirectory=”$(MSBuildProjectDirectory)“
ProjectName=”$(MSBuildProjectName)“
PackageVersion=”$(OctoPackPackageVersion)“
PrimaryOutputAssembly=”$(TargetPath)“
ReleaseNotesFile=”$(OctoPackReleaseNotesFile)“
NuGetExePath=”$(OctoPackNuGetExePath)“
NuGetProperties=”$(OctoPackNuGetProperties)“
NoDefaultExcludes=”$(OctoPackNoDefaultExcludes)" <<<<<<<<<<<<<<<
>
@@@