.Net publish doesn't copy Linux blink binaries to runtimes folder

[Burton Rodmam]

When I publish my .Net Core 6 project to a container, the blink binaries are copied to the root of the output path instead of to the runtimes/linux/native folder.

    <PackageReference Include="Syncfusion.HtmlToPdfConverter.Net.Linux" Version="21.2.5" />

This occurs locally if I run:

dotnet publish -c Release -r linux-x64 --self-contained

or when I public to a container in my CI pipeline:

- task: DotNetCoreCLI@2

  displayName: 'Publish Container'

  inputs:

    command: 'publish'

    projects: ${{ parameters.buildProjects }}

    publishWebProjects: false

    zipAfterPublish: false

    arguments: >-

      -c ${{ parameters.buildConfiguration }}

      -r linux-x64 --self-contained

      -p PublishProfile=DefaultContainer

      -p ContainerImageTags=$(Build.BuildId)

      -p ContainerRegistry=${{ parameters.containerRegistryHostname }}

      -v normal ${{ parameters.publishArguments }}

[Santhiya Narayanan]

On further analysis, when publishing the project without setting the runtime identifier (-r linux-x64 --self-contained), it will be published in the same structure.

 

If you want to set the runtime identifier, please set the runtime identifier and set the root folder as blinkpath in the blink converter settings.

[Burton Rodmam]

thanks for your reply.

the files in the locales folder are also placed in the root of bin.  should I expect any problems with this?

[Burton Rodmam]

also, do you intend to fix this behavior?

[Santhiya Narayanan]

Queries	Response
the files in the locales folder are also placed in the root of bin.  should I expect any problems with this?	No, we already ensured the conversion with this, there is no issues related to conversion.
also, do you intend to fix this behavior?	The runtime and native file copying are .NET behavior. So, we could not handle this in our side.

[Burton Rodmam]

do you intend to contact Microsoft about this behavior?

[Santhiya Narayanan]

The runtime file copying is a.NET behaviour that we can't control, but there is no issue in our conversion due to the file copying structure. Whether we set the runtime behaviour or not, it will work properly in the Volume 2 release.