This run is being retained as one of recent runs by main (Branch).
#20250310.4 • Bumps nanoFramework.TestFramework to 3.0.69
nanoframework.nf-Visual-Studio-extension
Triggered by nfbot
N
Repositories
2
Time started and elapsed
6m 56s
Related
0 work items 1 published; 1 consumed
Tests and coverage
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2424,5): Warning MSB3277: Found conflicts between different versions of "System.Reflection.Metadata" that could not be resolved.
There was a conflict between "System.Reflection.Metadata, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Reflection.Metadata, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
"System.Reflection.Metadata, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Reflection.Metadata, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.
References which depend on "System.Reflection.Metadata, Version=5.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Users\VssAdministrator\.nuget\packages\system.reflection.metadata\5.0.0\lib\net461\System.Reflection.Metadata.dll].
C:\Users\VssAdministrator\.nuget\packages\system.r VS2019 • VSBuild | |||
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2424,5): Warning MSB3277: Found conflicts between different versions of "System.IO.Pipelines" that could not be resolved.
There was a conflict between "System.IO.Pipelines, Version=5.0.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" and "System.IO.Pipelines, Version=5.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51".
"System.IO.Pipelines, Version=5.0.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" was chosen because it was primary and "System.IO.Pipelines, Version=5.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" was not.
References which depend on "System.IO.Pipelines, Version=5.0.0.1, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51" [C:\Users\VssAdministrator\.nuget\packages\system.io.pipelines\5.0.1\lib\net461\System.IO.Pipelines.dll].
C:\Users\VssAdministrator\.nuget\packages\system.io.pipelines\5.0.1\lib\net461\System.IO.Pipelines.dll
VS2019 • VSBuild | |||
C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2424,5): Warning MSB3277: Found conflicts between different versions of "Microsoft.VisualStudio.Shell.Framework" that could not be resolved.
There was a conflict between "Microsoft.VisualStudio.Shell.Framework, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "Microsoft.VisualStudio.Shell.Framework, Version=16.10.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
"Microsoft.VisualStudio.Shell.Framework, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "Microsoft.VisualStudio.Shell.Framework, Version=16.10.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.
References which depend on "Microsoft.VisualStudio.Shell.Framework, Version=16.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Users\VssAdministrator\.nuget\packages\microsoft.visualstudio.shell.framework\16.10.31321.278\li VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(295,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(381,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(590,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(699,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(837,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(968,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
vs-extension.shared\ToolWindow.DeviceExplorer\DeviceExplorerCommand.cs(1068,28): Warning VSTHRD100: Avoid "async void" methods, because any exceptions not handled by the method will crash the process. (https://github.com/Microsoft/vs-threading/blob/main/doc/analyzers/VSTHRD100.md) VS2019 • VSBuild | |||
View the log to see the remaining 22 warnings for this task | |||
Show 34 additional warnings | |||
Jobs
Name | Status | Duration | ||
|---|---|---|---|---|
Success | 17s | |||
Success | 5m 48s | |||
Success | 5m 19s | |||
Skipped | ||||
Sources
Repository | Branch / tag | Version | Related | ||
|---|---|---|---|---|---|
None | |||||
GitHub | |||||