8000 PLib: Allow building for .NET Standard 2.1 by Th3Fanbus · Pull Request #605 · peterhaneve/ONIMods · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

PLib: Allow building for .NET Standard 2.1 #605

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 2 commits into from
Jul 4, 2025

Conversation

Th3Fanbus
Copy link
Contributor

No description provided.

@peterhaneve
Copy link
Owner

Can you rebase on HEAD?

Th3Fanbus added 2 commits July 3, 2025 16:06
Wrap some stuff in preprocessor as it prevents compilation when using
.NET Standard 2.1 (which ONI now uses). The functionality in question
seems to be for debugging purposes only so it should not matter much.

Signed-off-by: Angel Pons <th3fanbus@gmail.com>
ONI now uses a cursed version of the Mono runtime that conforms to .NET
Standard 2.1 which does not have an exact Microsoft equivalent. But one
can still target the `netstandard2.1` framework while targetting a .NET
Framework v4 runtime. This is a bit (very) cursed, but somehow works...

I could not get MSBuild to behave the way I wanted it to, so I chose to
override `TargetFrameworks` in the various PLib projects one by one. It
is very likely there is a better way to go about this.

Signed-off-by: Angel Pons <th3fanbus@gmail.com>
@Th3Fanbus
Copy link
Contributor Author

I wanted to do a rebase but GitHub did a merge commit... Should be fine now.

@peterhaneve peterhaneve merged commit 641e5b7 into peterhaneve:main Jul 4, 2025
1 check passed
@peterhaneve
Copy link
Owner

Squashed the commits to avoid a mess with the merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0