Closed advapiIT closed 5 years ago
README
this is handled transparently by the new dotnet sdk as of LibLog version 5.0.0
are you using new a new style project with the dotnet sdk ?
no, on an old 4.6.1 library...
On Mon, Sep 9, 2019 at 2:00 PM Ruben Bartelink notifications@github.com wrote:
this is handled transparently by the new dotnet sdk as of LibLog version 5.0.0 are you using new a new style project with the dotnet sdk ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/damianh/LibLog/issues/260?email_source=notifications&email_token=ABDZBJTEN4R6SF7QBEAE5L3QIY3HRA5CNFSM4IUY4HOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6HJSFQ#issuecomment-529438998, or mute the thread https://github.com/notifications/unsubscribe-auth/ABDZBJTNMSW3BIQZNH7I5ZLQIY3HRANCNFSM4IUY4HOA .
this has come up in the issues in recent times, suggest looking for those threads. As per the readme, the advice is to use < 5 in that instance. (there may be other hackarounds suggested in those issues too) (Personally, I'd highly recommend to port projects to the new SDK sooner than later)
https://github.com/damianh/LibLog#availability-for-old-csproj-format
I don't have any way to make this easier/pit-of-success. There is no facility to detect attempting to install in old csproj format and give a nice error.
Hello, I'm trying to use LibLog 5.0.6 on a Framework 4.6.1 library, but it doesn't install.. where can I read which version of the framework is LibLog compatible with?
Thanks