.well-known folder missed from build

[adamzest]

We have a project with a structure like

\wwwroot
   \scripts
      ....
   \.well-known
       \apple-app-site-association
       \assetlinks.json

Running a standard dotnet publish copies the folder structure to the output folder.

Running dotnet publish /t:PublishContainer produces an image with the wwwroot\scripts structure but without the .well-known folder. I can find no way to overcome this.

I've had to rename the folder to 'well-known' (with the dot prefix) and use url rewriting to rewrite requests for .well-known to well-known

[baronfel]

@adamzest do you know what version of the .NET SDK or Container NuGet package you're using that you see this behavior in? I ask because we should have fixed this in dotnet/sdk#40624 back in May for .NET SDK 8.0.400 and onwards.

[adamzest]

The project is net8.0 and in my repro'ing of this today I am using SDK 8.0.405

[baronfel]

Thanks for the confirmation - we'll dig in.

[baronfel]

I'm not able to reproduce this on 8.0.405. I've made a dotnet new web application, added static files, added a wwwroot/.well-known/app.txt file and verified that during a local publish it ends up in the publish directory, and then I docker exec'd into the generated containers for both the 404 and 405 version of the app and both contain this file. Can you verify that the .well-known file ends up in your publish directory when you publish locally?

[adamzest]

Hi @baronfel

Thanks for looking. I just wrote out a really long response showing how I could still repro, and then I realised I'm an idiot. Of course in the linux container we are publishing, the .well-known folder is treated as hidden. ls -a and I can see it. So I would guess my problem all along was the file is present but hidden after publish, but AspNetCore isnt serving the static file because its hidden. Duh.

Sorry and thanks again.