.net - Why is Windows.Forms in System and not Microsoft? -


I always thought the root namespace in .net, " system " was primarily For which there was not much dependency on a particular platform.

I was thinking that anyone has any thoughts or insights, because Windows.Forms namespace system and not Microsoft because it seems pretty worn out in a platform.

(Any flame war or unnecessary MS Bass, please, if possible!))

I have read somewhere that the system * Namespace is for those things which are part of the core. Net structure, while Microsoft. * Nom place additional "Price-added" alternative extras, or things that are in development.

Edit:

Brad Abram has discussed this in his blog post

Additionally, A quote from Visual Basic 2005 refers to the .NET 3.0 programmer :

Microsoft-Root namespace contains Microsoft-specific items. In theory, any vendor intermediate language ( IL) can apply .Net languages ​​that translate into code. If you were to create such a language, then items in Microsoft Namespace would not normally apply to your language. Items in the system namespace ... will be useful for users of your language because those programmers who use Microsoft languages, but items in Microsoft's name space may not be useful.

This will mean that if I want to create a new net language, then I use the System.Windows.Forms namespace to create the UI Will be capable, but maybe I do not have Microsoft. * Too many uses for squares in namespaces.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -