what is .NET

  • Thread starter Thread starter vaibhav parashar
  • Start date Start date
The Microsoft .Net platform is a platform, which is the same thing as a
framework. It is an existing structure that you build on, in this case, a
software structure on which you build software. A framework is a skeletal
structure designed to enclose something, or as the basis for something
bulit. So, in essences, they are the same idea. In carpentry, for example,
you build a foundation which serves as a platform upon which you build a
house or building. The first part of the house that is built is the frame, a
structure which is skinned and finished, which forms the overall shape of
the house.

A technology, on the other hand, is a set of scientific principles and/or
systems, which are used in the construction of technical constructs, such as
software programs. The .Net platform is not a technology per se, but
contains a number of technologies, which are like the tools and techniques
used to build with.

--
HTH,

Kevin Spencer
Microsoft MVP
Ministry of Software Development
http://unclechutney.blogspot.com

Any experience you can walk away from
is a good one.
 
vaibhav said:
Dear all

Is .NET a Technolgical Platform
or

is it just a Framework

whats different b/w techonolgy and Framework

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Click to expand...

..NET is a set of object-oriented inherited components with a strict
hierarchical interface.

"technology" and "Technolgical Platform" are just meaningless
buzzwords. Framework refers to a set of rules which allow things to be
done in a certain way, which .NET most certainly provides.

Because .NET is so different than the erstwhile standards, it also
strongly suggests a different way to go about doing the same things.

B.
 
While .Net is "all the above" referring to all the previous replies, I had a
hard time moving to .Net in the early days until I finally began to see it as
simply a class library.

I struggled with the transition because I knew that .Net was supposed to be
this entirely new paradigm for developing software - and it is - but in its
simplest form, just think of it as a class library, or set of class
libraries, and Visual Studio .Net as a new IDE. Learning all the rest about
the CLR, IL, etc. Once I started with that little step, it allowed the rest
of it to begin to make sense to me.


Dale
 
MyOriginalPost.Replace(
"Learning all the rest about the CLR, IL, etc.",
"Learning all the rest about the CLR, IL, ect. can come later."
);
 
Dale said:
While .Net is "all the above" referring to all the previous replies, I had a
hard time moving to .Net in the early days until I finally began to see it as
simply a class library.
Click to expand...

I think that's a little too much simplification. While maybe strictly
true, Microsoft intends .NET to be used with IIS, AD, WMI and their
other related technologies to offer a competitive solution to J2EE.

Between Windows server technologies the framework, and all the .NET
programming models (web services, Windows services, web forms and
Windows forms), you're encapsulating similar functionality to servlets,
Javabeans/EJB, JSP, JDBC, Tomcat, JNDI, and more. Clearly, J2EE is more
than a class library, and therefore .NET running with the linked
services is more than a class library.

Would .NET be "simply a class library" if mscorlib.dll was separated
into System and everything else in System.*? I would think not, and the
mere inclusion of lots of libraries in a single assembly, invoking the
assembly vs. namespace argument, doesn't make them the same. Other than
that, the rest of the class library can be freely retrofitted, yet .NET
as a platform would still stand.


Stephan
 
Well, Microsoft claim it is their strategy for a web service driven system.

http://www.microsoft.com/net/basics.mspx

What many people think of as .Net is actually the Framework for creating
this system, although the system may not actually use any web services.
Somehow the newsgroups microsoft.public.dotnet.general and
microsoft.public.dotnet.framework seems almost identical.
 
Back
Top