You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
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.
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.
The move from
netstandard1.6
tonetstandard2.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 fornetstandard2.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
Castle.Facilities.Logging
#636)Castle.Facilities.Logging
#636)Tests
netstandard/net6
will require configuration to be manually applied rather than auto-loaded.(List taken from the README, there might be others in use, or some might have already been retired)
The text was updated successfully, but these errors were encountered: