Closed dhatrifork closed 6 years ago
Reproduce issue:
cd
into it.dotnet add package JavaScriptEngineSwitcher.ChakraCore.Native.win-x64 --version 2.4.15
dotnet build --runtime win7-x64 tutorial-code.csproj
.Chakracore.dll
is present in /bin/Debug/netcoreapp2.0/win7-x64/publish
.dotnet build --runtime win-x64 tutorial-code.csproj
.Chakracore.dll
is not present in /bin/Debug/netcoreapp2.0/win-x64/publish
.Renaming dirs and references from win7-*
to win-*
in local nuget-cache fixes it, and Chakracore.dll
ends up in both output dirs.
Hello!
Is there a reason for this?
There were compatibility issues. Microsoft.ChakraCore uses the same approach. I'll try to do some new tests.
If needs be, I can create a pull request?
Pull request is unnecessary.
This problem was solved in version 2.4.16.
It works now. Thanks! 👍
I need to use runtimeidentifier (RID)
win-x64
for my project, rather than (for example)win7-x64
orwin10-x64
, otherwise other packages break.This will not work with
JavaScriptEngineSwitcher.ChakraCore.Native.win-x64
nuget package, because theChakracore.dll
is inwin7-x64
dirs rather than plainlywin-x64
. Therefore, targetingwin-x64
RID will not copy theChakracore.dll
to the outputdir, and my cross-platform webapp using serverside-rendering does not work.Is there a reason for this? Could we not simply rename
win7-x64
towin-x64
and update references in buildfiles / propsfiles, and it would work? (The answer seems to be yes -- I've tried it by editing the files in my local nuget cache, and the small change does the trick).I assume there is a similar problem for
win-x86
vswin7-x86
.If needs be, I can create a pull request?