AdvancedSharpADBClient Nuget loads with error since Preview 2022.5 0685

[Hadasi]

Hi,
I’m experiencing problems with AdvancedSharpADBClient nuget.
Since version 0685 my patch fails to compile. It works okay with 0683. The console window pops up with this error:

EmitException: “error CS1705: Assembly ‘AdvancedSharpAdbClient’ with identity ‘AdvancedSharpAdbClient, Version=2.5.5.0, Culture=neutral, PublicKeyToken=null’ uses ‘Microsoft.Extensions.Logging.Abstractions, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60’ which has a higher version than referenced assembly ‘Microsoft.Extensions.Logging.Abstractions’ with identity ‘Microsoft.Extensions.Logging.Abstractions, Version=2.1.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60’”
StackTrace:
VL.Lang.Platforms.Roslyn.TargetCompilation+<>c__DisplayClass49_0 { internal System.ValueTuple<Microsoft.CodeAnalysis.AssemblyMetadata, VL.Core.RawAssembly> g__EmitDebug|0() { … } }
VL.Lang.Platforms.Roslyn.TargetCompilation { private System.ValueTuple<Microsoft.CodeAnalysis.PortableExecutableReference, VL.Core.RawAssembly> Emit(VL.Lang.Symbols.IProjectSymbol project, Microsoft.CodeAnalysis.CSharp.CSharpCompilation compilation, bool isDebug, bool includeSource, System.Threading.CancellationToken token) { … } }
VL.Lang.Platforms.Roslyn.TargetCompilation+<>c__DisplayClass6_0 { internal VL.Lang.Platforms.Roslyn.ProjectCompilation g__Build|0(VL.Lang.Platforms.Roslyn.ProjectBuildRequest projectBuildRequest) { … } }
VL.Lang.Platforms.Roslyn.TargetCompilation+<>c__DisplayClass6_1+<b__3>d { private virtual void MoveNext() { … } }
System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { … } }
VL.Lang.Platforms.Roslyn.TargetCompilation+d__6 { private virtual void MoveNext() { … } }
System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter1 { public TResult GetResult() { ... } } VL.Lang.Platforms.Roslyn.TargetCompilation+<CreateAsync>d__4 { private virtual void MoveNext() { ... } } System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { ... } } System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { ... } } System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { ... } } System.Runtime.CompilerServices.TaskAwaiter1 { public TResult GetResult() { … } }
VL.Lang.Platforms.Roslyn.TargetCompilation+d__45 { private virtual void MoveNext() { … } }
System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter1 { public TResult GetResult() { ... } } VL.Lang.Platforms.Roslyn.TargetCompilation+<VL-Lang-Symbols-ITargetCompilation-WithCompilationAsync>d__46 { private virtual void MoveNext() { ... } } System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { ... } } System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { ... } } System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { ... } } System.Runtime.CompilerServices.TaskAwaiter1 { public TResult GetResult() { … } }
VL.Model.VLSession+d__168 { private virtual void MoveNext() { … } }
System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { … } }
VL.Model.VLSession+d__167 { private virtual void MoveNext() { … } }
System.Runtime.ExceptionServices.ExceptionDispatchInfo { public void Throw() { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void ThrowForNonSuccess(System.Threading.Tasks.Task task) { … } }
System.Runtime.CompilerServices.TaskAwaiter { private static void HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) { … } }
VL.Model.VLSession+d__190 { private virtual void MoveNext() { … } }

It looks as though it having some conflict with references the that were installed with this package. I’ve tried removing and reimporting the Nuget but it still throws same error.

The package has many frameworks available, some of which depend upon Microsoft.Extensions.Logging.Abstractions, the dotnetcore frameworks using version 7 and some of the earlier frameworks using version 2

Any help would be very welcome.

H

[Elias]

vvvv.exe has an indirect dependency on Microsoft.Extensions.Logging through the usage of GitHub - daveaglick/Buildalyzer: A utility to perform design-time builds of .NET projects without having to think too hard about it. which was introduced in 0685.

Whenever our exe makes use of a specific library, the version is somewhat locked and you as a user can no longer freely select it. In an ideal world we’d make that information somewhat nicely accessible / visible, but for now I can only point you to the vvvv.deps.json file which shows those “locked” dependencies.

Upcoming builds will address your issue by referencing Microsoft.Extensions.Logging 7.0.0 directly.

[Hadasi]

Everything opens correctly with the last build. Thanks once again!