This article is rated Stub-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||
|
Base Class Library is much more commonly referred to than Framework Class Library, which is highly generic and should probably always be preceded by .NET. BCL has had an article for the last year, whereas FCL was just added and currently clones the other. It needs a lot of work to justify the dual articles -- if it can be justified. Template:DotNET should definitely link to BCL rather than FCL. -- David Gannon ( talk) 01:24, 12 December 2007 (UTC)
The BCL article contains namespaces outside its definition. It doesn't matter if people commonly refer to the FCL as the BCL, that doesn't turn the FCL into the BCL somehow. A lot of people say that Pepsi tastes like Coke, but we're not going to redirect Pepsi to Coke, are we? -- Stefán Örvarr Sigmundsson ( talk) 01:48, 12 December 2007 (UTC)
It looks like Base Class Library has already been incorporated into the Standard Libraries (CLI) article, even despite some pushback. (See above discussion.) So here's what should be an even less contentious proposal: this short, stubby article doesn't need to exist—it should be merged with the Standard Libraries, too (and be made to redirect there). AFAICS, the distinction between the "Framework Class Library" and the "Standard Libaries" is that the latter refers to the APIs defined in the relevant ECMA standards, and the former refers to the "classic" .NET Framework's implementation of those APIs. The distinction is too subtle and the article too old and its content to short to make any credible argument that this page deserves to exist on its own. So let's merge it. 2605:6000:1019:C064:5473:5A4:4724:3F07 ( talk) 19:46, 12 February 2019 (UTC)
This article is rated Stub-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||
|
Base Class Library is much more commonly referred to than Framework Class Library, which is highly generic and should probably always be preceded by .NET. BCL has had an article for the last year, whereas FCL was just added and currently clones the other. It needs a lot of work to justify the dual articles -- if it can be justified. Template:DotNET should definitely link to BCL rather than FCL. -- David Gannon ( talk) 01:24, 12 December 2007 (UTC)
The BCL article contains namespaces outside its definition. It doesn't matter if people commonly refer to the FCL as the BCL, that doesn't turn the FCL into the BCL somehow. A lot of people say that Pepsi tastes like Coke, but we're not going to redirect Pepsi to Coke, are we? -- Stefán Örvarr Sigmundsson ( talk) 01:48, 12 December 2007 (UTC)
It looks like Base Class Library has already been incorporated into the Standard Libraries (CLI) article, even despite some pushback. (See above discussion.) So here's what should be an even less contentious proposal: this short, stubby article doesn't need to exist—it should be merged with the Standard Libraries, too (and be made to redirect there). AFAICS, the distinction between the "Framework Class Library" and the "Standard Libaries" is that the latter refers to the APIs defined in the relevant ECMA standards, and the former refers to the "classic" .NET Framework's implementation of those APIs. The distinction is too subtle and the article too old and its content to short to make any credible argument that this page deserves to exist on its own. So let's merge it. 2605:6000:1019:C064:5473:5A4:4724:3F07 ( talk) 19:46, 12 February 2019 (UTC)