mfkl
Running awesome-lint locally on https://github.com/DopplerHQ/awesome-bots shows 770 errors full list here: https://gist.github.com/mfkl/32b9baf690e9b57642e9727ecbcb511b
I don't think libvlc supports setting custom headers
> I believe the underlying VLC Player + SDK was updated to support ARM64 sometime last year. That's true, but AFAIK it is a windows classic build not targetting UWP....
No reason, the github link works as well. Seen both asset store and github links in the readme but either work for me.
> Compile libvlc is a complicated matter You're right. Hopefully less so in the future. In the meantime, this might be of interest: https://nightlies.videolan.org/build/winrt-x86_64/vlc-x86_64-win10-20170413-0217.7z
``` 2021-03-01T06:19:47.8518930Z Using shared compilation with compiler from directory: /Library/Frameworks/Mono.framework/Versions/6.12.0/lib/mono/msbuild/Current/bin/Roslyn (TaskId:57) 2021-03-01T06:19:48.2074080Z Microsoft (R) Visual C# Compiler version 3.6.0-4.20224.5 (ec77c100) (TaskId:57) 2021-03-01T06:19:48.2075750Z Copyright (C) Microsoft Corporation. All rights reserved. (TaskId:57)...
Hmm, this seems to still be happening with .NET 6. It is currently not possible to have a single csproj file which targets both pre and post .NET 6 world....
Any news about this? Any workaround? I get the same message on Xamarin.Android `Only primitive types and IJavaObject is supported in array type in callback method parameter or return value`....
Hitting this as well with vmImage `vs2017-win2016` and `"MSBuild.Sdk.Extras": "2.0.54"` global json and .NET Core SDK `3.0.x`. Updating to the `windows-2019` vmImage fixes it for me.
Have a consistent repro here if you're interested @onovotny https://github.com/videolan/libvlcsharp/pull/71#issuecomment-540333184