|
|
Rank: Newbie
Groups: Member
Joined: 2/23/2021
Posts: 3
|
So I know that partial support was brought to netCore 2.0+ based on this post. https://www.essentialobjects.com/doc/common/dotnetcore.aspxI am currently migrating to net5 from Frameworks and so far the code is building and running fine and I am able to generate Pdf's from htlm. However I get a yellow warning icon in the dependencies folder saying "EO.pdf 21.0.32 was restored using '.NETFramework,Version=v4.6, .NETFramework,Version=v4.6.1. .NETFramework,Version=v4.7. .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8 instead of the project target framework net5.0. This package may not be fully compatible with your project. " This warning remains whether I target netcore 2.0 netcore 3.1 netstandard2.0 netstandard 2.1 and net5.0 however it successfully builds and runs each time. Is this warning a problem since I can still run everything with no issues or should I be concerned?
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
This is normal and you can ignore this message. .NET 5.0 is fully supported however because we use the same set of DLLs to support all platforms as oppose to have a separate set of DLLs for each platform, you will get that warning message. You can safely ignore the message.
Thanks!
|
|
Rank: Newbie
Groups: Member
Joined: 2/23/2021
Posts: 3
|
Oh okay that's good to know! So I can plan for the future, does Essential Objects plan on creating separate DLLS for each platform soon or in the future or is the plan to just stick to the same set of DLL's for now? Thanks for you help!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
Currently we do not have plan to create separate set of DLLs. Our DLLs are quite large because it contains the browser engine. So it is quite wasteful to have multiple set of DLLs in term of space. Instead we have code inside our DLLs to automatically detect different platforms and acts accordingly. The only downside of this approach is you would receive a warning message, which you can just ignore. To us this seems to be an acceptable trade off for shipping multiple sets of large DLLs that are 99.9% the same.
Thanks
|
|