You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our repo depends on two custom NuGet packages for .NET 6.0 C++/CLI components.
Both include a specific version of ijwhost.dll depending on the SDK used to build the packages.
This create double writes.
I guess there is no real problem at runtime, both versions should be compatible.
But we do not want to add explicit exclusions in our double write checker tool.
To Reproduce
ijwhost.dll is included in the nuspec with:
<file src="..." target="x64" />
And in the second package by putting ijwhost.dll in deps/netcore folder.
Fix attempts
Referencing Microsoft.NETCore.App.Host.win-64 in dependencies does not work (DotNetPlatform not supported)
frameworkReference in the nuspec does not work either (not recognized).
It seems the only option is to create a custom NuGet package including only ijwhost.dll.
Thanks for creating this issue! We believe this issue is related to NuGet tooling, which is maintained by the NuGet team. Thus, we closed this one and encourage you to raise this issue in the NuGet repository instead. Don’t forget to check out NuGet’s contributing guide before submitting an issue!
If you believe this issue was closed out of error, please comment to let us know.
Description
Our repo depends on two custom NuGet packages for .NET 6.0 C++/CLI components.
Both include a specific version of ijwhost.dll depending on the SDK used to build the packages.
This create double writes.
I guess there is no real problem at runtime, both versions should be compatible.
But we do not want to add explicit exclusions in our double write checker tool.
To Reproduce
ijwhost.dll is included in the nuspec with:
And in the second package by putting ijwhost.dll in deps/netcore folder.
Fix attempts
It seems the only option is to create a custom NuGet package including only ijwhost.dll.
See also #24310
The text was updated successfully, but these errors were encountered: