Skip to content

feat: Remove support for .NET 6.0, 7.0 #111

feat: Remove support for .NET 6.0, 7.0

feat: Remove support for .NET 6.0, 7.0 #111

Triggered via pull request December 20, 2024 01:38
Status Failure
Total duration 5m 14s
Artifacts

ci.yml

on: pull_request
Matrix: check-dotnet
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 30 warnings
.NET 9.0
Assets file 'D:\a\Parse-SDK-dotNET\Parse-SDK-dotNET\Parse.Tests\obj\project.assets.json' doesn't have a target for 'net9.0'. Ensure that restore has run and that you have included 'net9.0' in the TargetFrameworks for your project.
.NET 9.0
Process completed with exit code 1.
.NET 8.0
Process completed with exit code 1.
.NET 9.0: Parse/Infrastructure/Data/ParseDataEncoder.cs#L124
XML comment has badly formed XML -- 'End tag was not expected at this location.'
.NET 9.0: Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
.NET 9.0: Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
.NET 9.0: Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 9.0: Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 9.0: Parse/Platform/Cloud/ParseCloudCodeController.cs#L40
'Uri.EscapeUriString(string)' is obsolete: 'Uri.EscapeUriString can corrupt the Uri string in some cases. Consider using Uri.EscapeDataString for query string components instead.' (https://aka.ms/dotnet-warnings/SYSLIB0013)
.NET 9.0: Parse/Platform/Users/ParseCurrentUserController.cs#L95
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 9.0: Parse/Platform/Users/ParseUser.cs#L31
The variable 'ex' is declared but never used
.NET 9.0: Parse/Platform/Installations/ParseInstallation.cs#L171
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET 9.0: Parse/Platform/Objects/ParseObject.cs#L129
The variable 'ex' is declared but never used
.NET 8.0: Parse/Infrastructure/Data/ParseDataEncoder.cs#L124
XML comment has badly formed XML -- 'End tag was not expected at this location.'
.NET 8.0: Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
.NET 8.0: Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
.NET 8.0: Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 8.0: Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 8.0: Parse/Platform/Users/ParseCurrentUserController.cs#L95
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 8.0: Parse/Platform/Users/ParseUser.cs#L31
The variable 'ex' is declared but never used
.NET 8.0: Parse/Platform/Cloud/ParseCloudCodeController.cs#L40
'Uri.EscapeUriString(string)' is obsolete: 'Uri.EscapeUriString can corrupt the Uri string in some cases. Consider using Uri.EscapeDataString for query string components instead.' (https://aka.ms/dotnet-warnings/SYSLIB0013)
.NET 8.0: Parse/Platform/Installations/ParseInstallation.cs#L171
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET 8.0: Parse/Platform/Objects/ParseObject.cs#L129
The variable 'ex' is declared but never used
.NET 8.0: Parse/Infrastructure/Data/ParseDataEncoder.cs#L124
XML comment has badly formed XML -- 'End tag was not expected at this location.'
.NET 8.0: Parse/Infrastructure/Utilities/JsonUtilities.cs#L376
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'pre'.'
.NET 8.0: Parse/Infrastructure/Utilities/JsonUtilities.cs#L377
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
.NET 8.0: Parse/Infrastructure/Utilities/TaskQueue.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 8.0: Parse/Platform/Users/ParseCurrentUserController.cs#L28
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 8.0: Parse/Platform/Installations/ParseInstallation.cs#L171
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
.NET 8.0: Parse/Platform/Users/ParseUser.cs#L31
The variable 'ex' is declared but never used
.NET 8.0: Parse/Platform/Users/ParseCurrentUserController.cs#L95
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
.NET 8.0: Parse/Platform/Objects/ParseObject.cs#L129
The variable 'ex' is declared but never used
.NET 8.0: Parse/Platform/Cloud/ParseCloudCodeController.cs#L40
'Uri.EscapeUriString(string)' is obsolete: 'Uri.EscapeUriString can corrupt the Uri string in some cases. Consider using Uri.EscapeDataString for query string components instead.' (https://aka.ms/dotnet-warnings/SYSLIB0013)