In our solution we have a configuration file that is named something like this -
.MyApp.Speak.Important.config.
Basically, the name starts with a “.”(dot). This particular file is not getting deployed to the custom deployment directory. This file is not included in the nuget package that is created. I have checked that the content type of this file is “include”.
Could this be an issue with the process of creation of nuget package?
If you want to tell Octopack to pass the -NoDefaultExcludes switch to Nuget.exe, do it using /p:OctoPackNuGetArguments as shown in the Octopack documentation
I don’t think the parameters need to be separated by semicolons, but other than that it looks ok.
As for the repercussions, I believe that all files that are actually part of your app that start with a “.” will be added. It’ll be a matter of trying it on a test build and see what the package contains after that.