-
Notifications
You must be signed in to change notification settings - Fork 24
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
Removed platforms when supporting all platforms #183
Conversation
e3c6f18
to
297bd34
Compare
297bd34
to
76bed2c
Compare
Should we merge this after NLog 5.0 RTM? |
Would like to have this PR merged now to simplify the platform-list. This will allow me to prepare a PullRequest with the actual chances for NLog 5.0 RTM |
I think we should do that only for NLog 5? Doubting how to handle the NLog 4 docs |
Think all users expect that Dotnet support means Xamarin support. And with NLog v5 then default-values have been optimized for Xamarin and UWP platforms.
See no need for anything special to separate NLog v4 and v5, besides what is documented in the wiki pages.
|
What do you mean with "Dotnet"? .net standard, .net core, .net 5-6? |
All of them. The whole idea with Xamarin is using dotnet. And Microsoft have spent a lot of energy to unify it all with
|
@304NotModified Any chance for approval, so able to prepare the next pull-request? |
76bed2c
to
6672ff0
Compare
6672ff0
to
c2f7823
Compare
@304NotModified Any chance of this getting merge, so I can start on the documentation-updates for NLog 5.0 release? |
Initial step for resolving #182
Already now Target-Wrappers (Ex. AsyncWrapper) that are platform-agnostic does not specify platform-restrictions.
Also removed Xamarin iOS + Xamarin Android + Silverlight + WP8, as replaced by .NET Standard.