Green Living & Real Estate Marketing

November 17, 2008

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. 

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. 

3.) Part of the core redist vs. addons

System.* thinks it ships in the core redist.  You are not capable to embark it with your application.  System.* stuff only ships when the redist revs up.   You would not require Microsoft to do any out-of-band releases in the System.* namespace for example. 

Microsoft.* thinks it is not part of the core redist.   A note: as we go stuff into the core redist you’d require us to interchange the namespace from Microsoft.* to System.* thinking you’d have to fine-tune any ringing code *if* you needed to use up advantage of the newfangled version.

 

Indeed, what do you intend?  Which one best agrees your thoughts this?  I’d enjoy any other comments…

Related Posts:
Fω^C: a symmetrically classic variant of System Fω
Fω^C: a symmetrically Graeco-Roman variant of System Fω
Fω^C: a symmetrically authoritative variant of System Fω
My BailOut Solution - I’m In For At Least $50mm

Comments

The URI to TrackBack this entry is: http://statuska.blogsome.com/2008/11/17/what-does-that-net-namespace-mean-system-and-microsoft/trackback/

No comments yet.

RSS feed for comments on this post.

Leave a comment

Sorry, the comment form is closed at this time.






















Get free blog up and running in minutes with Blogsome
Theme designed by Hadley Wickham