Skip to content
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

Review conditional compilation symbols #631

Open
7 of 19 tasks
Jevonius opened this issue Oct 4, 2022 · 2 comments
Open
7 of 19 tasks

Review conditional compilation symbols #631

Jevonius opened this issue Oct 4, 2022 · 2 comments

Comments

@Jevonius
Copy link
Contributor

Jevonius commented Oct 4, 2022

The move from netstandard1.6 to netstandard2.0 has made some of the conditional compilation symbols obsolete. Using this issue as a place to track reviewing them. Depending on what fixes are needed, it might be that previously unavailable functionality can just be enabled for netstandard2.0/net6.0, or alternatively the functionality could be pulled out into extension nuget packages and left as optional (if enabling the functionality involves additional nuget packages for example).

Code

Tests

(List taken from the README, there might be others in use, or some might have already been retired)

@Jevonius Jevonius mentioned this issue Oct 4, 2022
6 tasks
@Jevonius Jevonius changed the title Review of potentially obsolete conditional compilation symbols Review conditional compilation symbols Oct 5, 2022
@Jevonius
Copy link
Contributor Author

Jevonius commented Oct 5, 2022

A few of these could be removed by using built-in symbols (such as NETFRAMEWORK) instead of defining custom symbols (FEATURE_CODEDOM and FEATURE_THREADABORT, potentially others).

Is there a preference one way or the other? Personal preference would be to use built-in where possible.

@jonorossi
Copy link
Member

Originally I put all these symbols in when we first started with DNX (to become .NET Core 1.0), back then the API surface was very small and constantly changing while in preview. If we can get rid of heaps of these either through not needing them any more or removing the feature, happy for you to use in-built symbols which didn't exist in the original tooling.

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

No branches or pull requests

2 participants