-
-
Notifications
You must be signed in to change notification settings - Fork 23
add .net 8 support, remove netcore3.1 support #89
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
71a0719
add .net 8 support
tanordheim c8e75f7
drop netcore3.1 support
tanordheim 9e1153d
temp: notes
tanordheim 3c8aab9
chore: change eng scripts to install correct sdks
leonardochaia ff0642d
chore: remove netcoreapp3 packages
leonardochaia 0fb8adc
chore: removes netcoreapp3 condition
leonardochaia 0aeae47
fix: tests for net8.0
leonardochaia 2af239b
fix: ci build by building in release
leonardochaia 22cbf5d
ci: fix build
leonardochaia File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| { | ||
| "sdk": { | ||
| "version": "7.0.101", | ||
| "version": "8.0.100", | ||
| "allowPrerelease": true | ||
| } | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
80 changes: 0 additions & 80 deletions
80
src/DotnetAffected.Core/Processor/AffectedProcessorLegacy.cs
This file was deleted.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -254,7 +254,7 @@ as they don't actually build projects, they just delegate the build to a differe | |
| own configuration. | ||
|
|
||
| However, `DotnetAffected.Tasks` itself contains code to execute in build time, which | ||
| support TFMs `netcore3.1`, `net6.0` and `net7.0`. | ||
| support TFMs `net6.0`, `net7.0` and `net8.0`. | ||
|
|
||
| The TFM must be known so the proper TFM facing assembly is used. | ||
|
|
||
|
|
@@ -265,6 +265,7 @@ In most cases it is automatically resolved using the following logic: | |
| - If >= `17.0.0` it will resolve to `net6.0` | ||
| - Else if >= `16.11.0` it will resolve to `net5.0` | ||
| - Else it will resolve to `netcoreapp3.1` | ||
| - TODO | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure how true this list is at the moment, I'm not that intimately familiar with how all of this stuff works. How would you suggest I change this? |
||
|
|
||
| If you have issues, you can override the logic by specifically setting the `<TargetFramework>`. | ||
|
|
||
|
|
@@ -278,5 +279,5 @@ If you have issues, you can override the logic by specifically setting the `<Tar | |
| ``` | ||
|
|
||
| > `DotnetAffected.Tasks` provides MSBuild integration using `DotnetAffected.Core` under the hood. | ||
| `DotnetAffected.Core` support TFMs `netcore3.1`, `net6.0` and `net7.0`. | ||
| `DotnetAffected.Core` support TFMs `net6.0`, `net7.0` and `net8.0`. | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When running these tests locally I more or less always (but I have also seen it succeed I think) get this error for the
net8.0target. All other targets pass just fine:I'm not sure why this only fails on
net8.0and notnet6.0andnet7.0. What seems to solve it is to add this to theProjectOptionsbelow:The tests for non-
net8.0frameworks still pass with this in place but I'm not sure this is the correct fix. Any thoughts on this?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @tanordheim , as you pointed out they were failing due to missing
TargetFramework.I've added it in the sample project generation in tests and that seems to work