Skip to content

Build

Build #10

Manually triggered April 21, 2024 23:54
Status Success
Total duration 12m 48s
Artifacts 9

build.yml

on: workflow_dispatch
Matrix: build / build-test
build  /  sign-nuget
0s
build / sign-nuget
build  /  upload-artifacts
30s
build / upload-artifacts
Fit to window
Zoom out
Zoom in

Annotations

70 warnings
build / package: HeroesData/App.cs#L305
Use 'string.StartsWith(char)' instead of 'string.StartsWith(string)' when you have a string with a single char (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1867)
build / package: HeroesData/ExtractorImages/ImageVoiceLine.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageUnit.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageTypeDescription.cs#L29
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageSpray.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageMatchAward.cs#L23
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageSpray.cs#L53
Use recommended dispose pattern to ensure that object created by 'GetDDSImage(filePath)' is disposed on all paths. If possible, wrap the creation within a 'using' statement or a 'using' declaration. Otherwise, use a try-finally pattern, with a dedicated local variable declared before the try region and an unconditional Dispose invocation on non-null value in the 'finally' region, say 'x?.Dispose()'. If the object is explicitly disposed within the try region or the dispose ownership is transfered to another object or method, assign 'null' to the local variable just after such an operation to prevent double dispose in 'finally'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2000)
build / package: HeroesData/ExtractorImages/ImageHero.cs#L29
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/App.cs#L756
Change type of variable 'xmlDataService' from 'HeroesData.Parser.XmlData.IXmlDataService' to 'HeroesData.Parser.XmlData.XmlDataService' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)
build / package: HeroesData/ExtractorImages/ImageExtractorBase.cs#L181
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/App.cs#L305
Use 'string.StartsWith(char)' instead of 'string.StartsWith(string)' when you have a string with a single char (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1867)
build / package: HeroesData/ExtractorImages/ImageVoiceLine.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageUnit.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageTypeDescription.cs#L29
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageSpray.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageMatchAward.cs#L23
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageSpray.cs#L53
Use recommended dispose pattern to ensure that object created by 'GetDDSImage(filePath)' is disposed on all paths. If possible, wrap the creation within a 'using' statement or a 'using' declaration. Otherwise, use a try-finally pattern, with a dedicated local variable declared before the try region and an unconditional Dispose invocation on non-null value in the 'finally' region, say 'x?.Dispose()'. If the object is explicitly disposed within the try region or the dispose ownership is transfered to another object or method, assign 'null' to the local variable just after such an operation to prevent double dispose in 'finally'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2000)
build / package: HeroesData/ExtractorImages/ImageHero.cs#L29
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/App.cs#L756
Change type of variable 'xmlDataService' from 'HeroesData.Parser.XmlData.IXmlDataService' to 'HeroesData.Parser.XmlData.XmlDataService' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)
build / package: HeroesData/ExtractorImages/ImageExtractorBase.cs#L181
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/App.cs#L305
Use 'string.StartsWith(char)' instead of 'string.StartsWith(string)' when you have a string with a single char (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1867)
build / package: HeroesData/ExtractorImages/ImageVoiceLine.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageUnit.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageTypeDescription.cs#L29
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageSpray.cs#L28
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageMatchAward.cs#L23
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageSpray.cs#L53
Use recommended dispose pattern to ensure that object created by 'GetDDSImage(filePath)' is disposed on all paths. If possible, wrap the creation within a 'using' statement or a 'using' declaration. Otherwise, use a try-finally pattern, with a dedicated local variable declared before the try region and an unconditional Dispose invocation on non-null value in the 'finally' region, say 'x?.Dispose()'. If the object is explicitly disposed within the try region or the dispose ownership is transfered to another object or method, assign 'null' to the local variable just after such an operation to prevent double dispose in 'finally'. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2000)
build / package: HeroesData/ExtractorImages/ImageHero.cs#L29
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageExtractorBase.cs#L181
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)
build / package: HeroesData/ExtractorImages/ImageExtractorBase.cs#L194
Use 'ArgumentNullException.ThrowIfNull' instead of explicitly throwing a new exception instance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1510)

Artifacts

Produced during runtime
Name Size
HeroesData-Nuget Expired
1.44 MB
HeroesData-fdd-any (tar) Expired
1.49 MB
HeroesData-fdd-any (zip) Expired
1.44 MB
HeroesData-fde-linux-x64 Expired
1.46 MB
HeroesData-fde-osx-x64 Expired
1.46 MB
HeroesData-fde-win-x64 Expired
1.45 MB
HeroesData-scd-linux-x64 Expired
29.2 MB
HeroesData-scd-osx-x64 Expired
29.2 MB
HeroesData-scd-win-x64 Expired
28.8 MB