-
Notifications
You must be signed in to change notification settings - Fork 170
Fix Build Failure #316
New issue
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
Fix Build Failure #316
Conversation
bfeb47c to
2296d3c
Compare
|
Updating checkout to v3 and setup dotnet to v2 |
66407d9 to
74d3fc3
Compare
|
After adding the props file in, it caused the ubuntu and windows builds to fail which is interesting since that means adding in a props file fails on dotnet 5 (the build is here: https://github.com/IntelliTect/EssentialCSharp/runs/7532253715?check_suite_focus=true) but after adding in a global.json and installing the dotnet 6 sdk onto the machine, then it passes for all builds. (https://github.com/IntelliTect/EssentialCSharp/runs/7532292828?check_suite_focus=true). |
src/Chapter10/Listing10.23.RegisteringAFinalizerWithProcessExit.ps1
Outdated
Show resolved
Hide resolved
|
So currently we do need a global.json because we ended up with failures on dotnet 5 of "warningCS8632:Theannotationfornullablereferencetypesshouldonlybeusedincodewithina'#nullable'annotationscontext.". I have a suspicion this is because with the directory props file being empty, when the csproj file is being generated, it by default has nullability disabled. I am testing this theory by adding it to be enabled in the pwsh script here: #318 . If it passes, I will get to drop the globl.json in this pr and just instead add nullability to the pwsh script for the props file. |
…t.ps1 Co-authored-by: Kevin B <Keboo@users.noreply.github.com>
eac196d to
b4480f3
Compare
src/Chapter10/Listing10.23.RegisteringAFinalizerWithProcessExit.ps1
Outdated
Show resolved
Hide resolved
…t.ps1 Co-authored-by: Kevin B <Keboo@users.noreply.github.com>
…tupdatingdotnetsdks
fixes #312