What Does that .NET Namespace Mean: System.* and Microsoft.*
I take your feedback… I am chatting with some co-workers about the perception of in the.NET Community of what the System.* and Microsoft.* namespaces mean. So I had the wild idea of but expecting you!
For this exercise, I’d care you to flirt with a newfangled "feature area" of the.NET Framework… Would you instinctively make any conclusions about that area grounded on if the namespace where System.* or Microsoft.*? If that feature area were in the Silverlight subset of.NET, would that interchange your mind at all?
There are fundamentally three schools of thought among my co-workers — which one is closer to your perception?
1) They are the same or it truly doesn’t matter. The root namespace between System.* and Microsoft.* have no meaning… Microsoft seems to be arbitrary about when functionality gos in one or the other.
2) Part of the Framework vs. Addons.
(more…)System.* argues stuff that is logically part of the framework. It is 100% sustained, self-coloured-longsighted term design that will not call for to moil, good to look on, stable, probably will catch outstanding joyriding support. Contrived to be very interoperable and could act anyplace.NET is. This may embark as part of the redist or perhaps an out of band (such as ASP.NET MVC, ASP.NET AJAX, etc).
Microsoft.* is the runing edge stuff or value-add. It is typically very nerveless stuff that supplies on to the framework and raises it, but perchance a work in progress… over time you might require some of those concepts to enter the framework. As an example, the outstanding work patterns and practices does a great deal falls under this bucket.
