Template talk:.NET Framework version history

Suggest an alternative revision
About date format, because .net framework is a product of Microsoft, a North American international corporation. In order to avoiding the confusion, using American Standard Date format to state its precise release date.

This revision is provided for kind and nice editors from all over the world who want to improve the template in the main article. Any critic is welcome, but modifications to it for improving its qualities are much more welcome. But I do anti-"Nazi"! Janagewen (talk) 00:31, 19 November 2014 (UTC)


 * For involving modifying this template I have experienced being blocked twice, and I try to replace it with my revision, it was reverted for more than 3 times. If you, any reader, not a stupid or woodenhead, you would find it is the most ridiculous template stating information on .net framework. All the seemed-reasonable references attached to that template is the just the confusion for its original writer about .net framework. Guys, here, Jeh, Codename Lisa and Fleetcommand are worse. I just wish there would be someone would balance the balance, not to mislead readers too much.   Janagewen (talk) 23:22, 21 November 2014 (UTC)


 * If you start labeling people "woodenhead" (whatever that means) instead of listening to them, you end up in world full of woodenheads that has no "reader" in it. Your table is horribly vague and your English language is awful. You should have gotten the hint when you were blocked the first time. — Preceding unsigned comment added by 46.62.182.2 (talk) 06:22, 22 November 2014 (UTC)

But have we ever both chatted on wiki? Why omitted your name here? If you are English-native speaker, then I am sorry. If not, why you use awful to describe my English skill? That takes nonsense, I think I was treated as shit for each my modification on this template has been reverted in minutes without reason. Can I call it discrimination? I was treated in this way like a shit, so no matter my English skill is awful or excellent, does it take sense? The template in main article is obviously a mass, and misleads readers, especially on the description about the relationship among versions and inclusion. That is wrong! I know people passed it by and ignored, or without passion to modify it, but not say that it is correct. Yeah, I apologize for using the words "woodenhead" and "stupid", but these two words are the most suitable for people who ignore my revision and reverted my modification without consideration at all. Guy, if you are interested in this template too, I just wish you devote to making it better rather than arguing some a shit like me. Janagewen (talk) 07:31, 22 November 2014 (UTC)

Why should I always give a shit? Janagewen (talk) 10:42, 22 November 2014 (UTC) ✅

https://social.msdn.microsoft.com/Forums/vstudio/en-US/145e8605-899e-4014-934a-0d1f877410b0/which-table-is-more-reasonable?forum=netfxsetup The above link might be the only proof worth mentioning here. Password Saeba Ryo (talk) 04:59, 27 December 2014 (UTC)

A good suggestion! I love it! — Preceding unsigned comment added by 85.236.156.206 (talk) 03:41, 8 February 2015 (UTC)

End of support column
I thought I would suggest adding a new column specifying end of support dates based on something like "Microsoft .NET Framework Support Lifecycle Policy FAQ". The reason is that specifies a complex end of support schedule based on different versions having been released differently (either independent product or component of something else like an OS release, etc.). 15.203.233.84 (talk) 23:33, 30 November 2015 (UTC)
 * Oppose. Hello! I have three reasons for opposing:
 * 1) As the source you gave says, .NET Framework support follows the support lifecycle policy of the parent operating system. We already have three templates in Wikipedia showing that. There is already too much emphasis on Windows support in Wikipedia.
 * 2) The underlying article does not discuss the support status in a meaningful manner. Without such an elucidation, WP:IINFO comes into play; Wikipedia is not a collection of dates for the sake of collecting dates.
 * 3) Most importantly, there is nothing encyclopedic to be said about the support for individual versions of .NET Framework. And that's exactly why Microsoft considers the framework a component. I'll keep an open mind, however, in case you can show me an example.
 * Best regards,
 * Codename Lisa (talk) 06:00, 1 December 2015 (UTC)

Pro argument: The FAQ does say that the support depends on the underlying OS, but on the same time states that "support will end for .NET Framework 4, 4.5, and 4.5.1 on January 12, 2016.". The support for version 4.5.1 is thus shorter as the one of 8.1 and 2012 R2: 4.5.2 is considered as a fix of previous 4.x version. As of August 2016, 4.5.2 is thus the oldest version still supported and probably therefore the default version in Visual Studio 2015 update3! EDIT: 3.5 is still supported as part of Windows 7 — Preceding unsigned comment added by 195.65.52.7 (talk) 12:36, 23 August 2016 (UTC)

Importance of .NET Standard
The importance of .NET Standard is that it a unifying concept between .NET Core and .NET Standard. This will be clear when .NET Standard 2.0 will be released because it the first version that will be compatible with both of: a version of .NET Framework (v 4.6.1) and a version of .NET Core ( v 2.0) Its release date is Q3 2017. Saying that, I would ask for not reverting [| my edit] of this template that added a column containing .NET Standard read (talk) 18:24, 29 March 2017 (UTC)
 * Hello,
 * Did you study our WP:IINFO policy?
 * What you say is the importance of the standard itself, not the significance of the values you wrote in the table. Those values communicate zero meaning to the ordinary reader because they are not put in context. Without context, they have zero meaning for the reader.
 * Best regards, Codename Lisa (talk) 23:39, 29 March 2017 (UTC)