A hub and casual space for you to interact with fellow community members and learn more about Umbraco!

Umbraco

it appears to be something to do with attempting to dotnet pack with --no-build

I think NuGet defaults to both folders (due to legacy support IRC). I keep this in my .csproj file:

https://github.com/skybrud/Skybrud.Umbraco.Redirects/blob/v3/main/src/Skybrud.Umbraco.Redirects/Skybrud.Umbraco.Redirects.csproj#L6

for the issue I was having it isn't about content vs contentFiles it's the fact that either exist in the first place as the assets should be expected to be in staticwebassets.
I'm not exactly sure what's up with it but if ran as `build` followed by`pack --no-build` one of the pack targets ends up outputting a list of files with both the absolute paths and the the relative paths and we end a tripple sized nupkg.
but running `pack` omitting `--no-build` everything works as expected, no content or contentFiles only staticwebassets which is fixed enough for me not to lose any sleep over it.