Skip to content
.NET

Use reference types instead of value types for memory efficiency #7

Sign in to view logs

Use reference types instead of value types for memory efficiency

Use reference types instead of value types for memory efficiency #7

Triggered via push November 15, 2024 18:29
@ricardobossricardoboss
pushed b4f7845
main
Status Success
Total duration 3m 33s
Artifacts 3

dotnet.yml

on: push
Test
28s
Test
Matrix: publish
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Publish for linux-x64
Spectre.Console.Cli.CommandModel.GetApplicationFile(): 'System.Reflection.Assembly.Location.get' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
Publish for linux-x64
System.Net.Quic.MsQuicApi..cctor(): 'System.Reflection.Assembly.Location.get' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
Publish for osx-x64
Spectre.Console.Cli.CommandModel.GetApplicationFile(): 'System.Reflection.Assembly.Location.get' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
Publish for win-x64
Spectre.Console.Cli.CommandModel.GetApplicationFile(): 'System.Reflection.Assembly.Location.get' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.

Artifacts

Produced during runtime
Name Size
publish-linux-x64
23.6 MB
publish-osx-x64
30.3 MB
publish-win-x64
29.6 MB