Add net8 testing #55
gdziadkiewiczAnnotations
30 errors and 30 warnings
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (macOS-13)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (windows-latest)
The type or namespace name 'NUnit' could not be found (are you missing a using directive or an assembly reference?)
|
|
build (ubuntu-latest):
build/build.fs#L229
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L236
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L239
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L242
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L245
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L248
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L252
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L257
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L260
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (ubuntu-latest):
build/build.fs#L263
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L229
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L236
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L239
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L242
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L245
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L248
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L252
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L257
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L260
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (macOS-13):
build/build.fs#L263
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L229
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L236
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L239
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L242
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L245
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L248
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L252
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L257
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L260
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|
|
build (windows-latest):
build/build.fs#L263
The result of this expression has type 'string' and is implicitly ignored. Consider using 'ignore' to discard this value explicitly, e.g. 'expr |> ignore', or 'let' to bind the result to a name, e.g. 'let result = expr'.
|