We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build started... 1>------ Build started: Project: Seatbelt, Configuration: Debug Any CPU ------ 1>C:\Users\Lalit\Source\Repos\Seatbelt\Seatbelt\Commands\Misc\LOLBAS.cs(130,27,130,31): error CS8618: Non-nullable property 'Path' must contain a non-null value when exiting constructor. Consider declaring the property as nullable. ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
WriteVerbose($"Found: {query.Count()} LOLBAS"); WriteHost("\nTo see how to use the LOLBAS that were found go to https://lolbas-project.github.io/"); }
internal class LolbasDTO : CommandDTOBase {
line 130: public string Path { get; set; }
The text was updated successfully, but these errors were encountered:
Are you using the latest version of Seatbelt from Github? The LOLBAS constructor initializes that value in the current code. See https://github.com/GhostPack/Seatbelt/blob/master/Seatbelt/Commands/Misc/LOLBAS.cs#L128-L135
Sorry, something went wrong.
No branches or pull requests
Build started...
1>------ Build started: Project: Seatbelt, Configuration: Debug Any CPU ------
1>C:\Users\Lalit\Source\Repos\Seatbelt\Seatbelt\Commands\Misc\LOLBAS.cs(130,27,130,31): error CS8618: Non-nullable property 'Path' must contain a non-null value when exiting constructor. Consider declaring the property as nullable.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
WriteVerbose($"Found: {query.Count()} LOLBAS");
WriteHost("\nTo see how to use the LOLBAS that were found go to https://lolbas-project.github.io/");
}
line 130: public string Path { get; set; }
The text was updated successfully, but these errors were encountered: