Copy Cef/CefSharp into sub folder, does not work

[trivalik]

I converted my project to new .NET Core SDK style projects (still compiling agains .NET Framework 4.8), with use of CefSharp 86, all is fine. CefSharp is in sub folder copied. Also if I build a project without Cefsharp in it but a dependency is using it.
Now I want to update to CefSharp 89, found that building projects which depends on this CefSharp works fine, but projects without direct CefSharp reference (nuget package) which rely on these projects with CefSharp dependency do now copy the cef binaries direct into OutputDir. This is because of the _TransitiveItemsToCopyToOutputDirectoryPreserveNewest --> PreserveNewest lead to copy it to output directory.

I guess it started since CefSharp 87. CefSharp 90.5.70-pre has no real change here, so it should have same issue.

I read about DisableTransitiveProjectReferences, but this is not working somehow.

Edit:

One workaround would to define CefSharpTargetDir this these projects too, but this will be getting dependency hell.

[amaitland]

Now I want to update to CefSharp 89, found that building projects which depends on this CefSharp works fine, but projects without direct CefSharp reference (nuget package) which rely on these projects with CefSharp dependency do now copy the cef binaries direct into OutputDir.

Issue #3319 has details on the nuget package restructure. In particular #3319 (comment)

I read about DisableTransitiveProjectReferences, but this is not working somehow.

I'm not familiar with that particular option, please provide a reference link.

One workaround would to define CefSharpTargetDir this these projects too, but this will be getting dependency hell.

The preferred option in my opinion is to use a Directory.Build.props file as I've described in #3319 (comment)

You can set <CefSharpTargetDir/> in a solution wide basis if required. The example I used was for <CefSharpAnyCpuSupport/> the same fundamentals apply to <CefSharpTargetDir/>.

You can also set <CefSharpBuildAction /> to NoAction for projects you don't want to copy any of the files into output folder, this is particularly useful for Library projects where you only require the files in the Exe/WinExe projects. Save compile time/disk space.

<CefSharpBuildAction Condition="'$(OutputType)' == 'Library'">NoAction</CefSharpBuildAction>

which rely on these projects with CefSharp dependency do now copy the cef binaries direct into OutputDir

That is the expected default when using a Sdk Style project, the default is that buildTransitive assets flow through to consuming projects so reference libraries can consume the projects without requiring a direct reference.

You can set <CefSharpBuildAction/> to None and control the Control the dependency assets using the <PackageReference/> element. to effectively revert to the old pre version 87 behavior, though the preferred option in my opinion is a Directory.Build.props file.

[trivalik]

I have no real reference for DisableTransitiveProjectReferences, maybe is it only really working for old style project.

I forgot to tell, that I am targeting only x86 right know.

Adding Directory.Build.props to solution directory to prevent copy (https://curia.me/net-core-transitive-references-and-how-to-block-them/) is not the trick.

I did for every direct reference this:

<PackageReference Include="cef.redist.x86" Version="89.0.17">
  <PrivateAssets>all</PrivateAssets>
</PackageReference>
<PackageReference Include="CefSharp.WinForms" Version="89.0.170">
  <PrivateAssets>all</PrivateAssets>
  <ExcludeAssets>runtime</ExcludeAssets>
</PackageReference>

<ExcludeAssets>runtime</ExcludeAssets> prevent copy to output directory. Then I copied them manually into the sub folder.

Edit:
seems now also working without PackageReference Include="cef.redist.x86

[amaitland]

Adding Directory.Build.props to solution directory to prevent copy (https://curia.me/net-core-transitive-references-and-how-to-block-them/) is not the trick.

What do you mean by this? Did you try it and it didn't work? If so what did you try? Where did you put the file? Please provide detailed responses.

I did for every direct reference this:

For PackageReference you need only include the top level package, keep CefSharp.Winforms and remove the other CefSharp packages.

I don't know the exact values you need, you will also need to set <CefSharpBuildAction/> to None so the files are included as they were in previous version.

[trivalik]

using just this setting for every project which uses CefSharp:

  <ItemGroup>
    <PackageReference Include="CefSharp.WinForms" Version="89.0.170" />
  </ItemGroup>
  <PropertyGroup>
    <CefSharpTargetDir>CefSharp</CefSharpTargetDir>
    <CefSharpBuildAction>None</CefSharpBuildAction>
  </PropertyGroup>

still copies cef.pak, and co. into target folder. Also CefSharp.WinForms.dll and co. is not inside the CefSharpTargetDir.
Anyway, my solution works for now. Thanks for your time. In case you want to improve here, I can test.

[amaitland]

using just this setting for every project which uses CefSharp:

You also need to make buildTransative a private asset.

https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#controlling-dependency-assets

CefSharp.WinForms.dll and co. is not inside the CefSharpTargetDir.

As per #3319 that is expected, CefSharp.Winforms.dll, CefSharp.dll and CefSharp.Core.dll now target AnyCpu and are added as direct references to the project by Nuget, they cannot be moved by CefSharpTargetDir. You can add a custom post build action if you absolutely have to move these files.

In case you want to improve here, I can test.

Did you test with a Directory.Build.props file? What did your file include?

[trivalik]

I tried it but without <ExcludeAssets>runtime</ExcludeAssets> are files still copied. With my above settings does it work.

[amaitland]

will copy Cef double

What files exactly are you referring?

Please confirm you've read https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files#controlling-dependency-assets

[trivalik]

I read this. It copied the whole Cef folder twice, because of different path of CefSharpTargetDir. To fix this without remove, I have probably to add CefSharp.Common dependency to disable this copy. Anyway, to keep it simple I let the remove directory in.

[amaitland]

Is there a reason you don't use a Directory.Build.props file to set CefSharpTargetDir for all your projects?

[trivalik]

I did, but the test project have to emulate the same directory structure, else the test would fail.
Maybe I missed in example to move it to root folder, but this would make no difference.

[Xan-Kun]

I tried the way given in #3319 (comment) and others and none of them work. The files are copied to the bin folder at publish every time.

Is there a working example using Directory.Build.props AND CefSharp.WinForms.NETCore somewhere that I might have missed?

[Xan-Kun]

I have a WinForm project using CefSharp.WinForms.NETCore (124.3.80).
The target is win-x64 with net8.0-windows7.0.

I can't get it to copy to a subfolder. And I am a little confused about what the correct way in this case would be.
In the end, I need to get libGLESv2.dll out of the way because it causes problems with other packages.

Any help/hint much appreciated.

[trivalik]

I guess you have then to disable the copy by CefSharp packages and manage this manuell file for file.

[Xan-Kun]

I dont know how to disable the copy, but i understand the idea.

[amaitland]

I have a WinForm project using CefSharp.WinForms.NETCore (124.3.80).

CefSharpTargetDir is not supported by the NETCore packages. The packages use Architecture-specific folders to comply with the nuspec standard.

When the .Net Framework packages were created, this feature wasn't available, so we copied the files manually, CefSharpTargetDir allowed for customisation of this copy. The NETCore packages rely on MSBuild copy all files (except locales). This allows us to use built in features like Controlling dependency assets

I dont know how to disable the copy, but i understand the idea.

See NuGet/Home#5986

[Xan-Kun]

Thanks for the comment, I know those already, but they dont really apply. As I understand it, it allows for control on a pe-file basis. (Please correct me if i'm wrong), which is kinda the opprosite of what CefSharpTargetDir was doing.
This approach seems very tideous and error-prone.
How could we reliable tell the difference between the managed dlls, that we need in the binary folder and the "extra" files only for the browser subprocess?

[Xan-Kun]

I think it would be fair to answer at least one of the many questions on the web concerning this with a truthful: NO.
Not in CefSharp.WinForms.NETCore.