Talk:Framework Class Library

Note to self, remember to add these and more to the list:

System.AddIn.Contract
System.AddIn.Hosting
System.AddIn.Pipeline
System.Collections.Generic
System.ComponentModel
System.Configuration
System.Diagnostics
System.Diagnostics.Eventing
System.Diagnostics.Eventing.Reader
System.Diagnostics.PerformanceData
System.DirectoryServices
System.DirectoryServices.ActiveDirectory
System.EnterpriseServices
System.Globalization
System.IdentityModel.Claims
System.IO
System.IO.Compression
System.IO.IsolatedStorage
System.IO.Pipes
System.IO.Ports
System.Linq
System.Linq.Expressions
System.Reflection
System.Reflection.Emit
System.Resources
System.Runtime.Serialization
System.Runtime.Serialization.Json
System.Security
System.Security.AccessControl
System.Security.Cryptography
System.Security.Cryptography.X509Certificates
System.Security.Principal
System.ServiceProcess
System.Text
System.Text.RegularExpressions
System.Threading
System.Transactions

--Stefán Örvarr Sigmundsson (talk) 20:52, 11 December 2007 (UTC)[reply]

BCL vs. FCL

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)[reply]