Newby question.

[Stan Blazejewski]

Can someone explain (in plain english) what .NET framework is/does and why I
should install it even though this computer is working fine without it.

I have had a read of MS's 'what is .NET framework' which seemed to be vague &
unspecific and left me none the wiser.

Thanks in advance.

--

Australia isn't "down under", it's "off to one side"!

(e-mail address removed)
www.cobracat.com (home of the Australian Cobra Catamaran)
http://groups.yahoo.com/group/cobra-cat/

 

[Patrice]

You'll have to install this only if you want to use an application that
requires it.

It provides to .NET based applications easier, wider and unified access to
Windows capabilities.

 

[Nick Hounsome]

Fundamentally it is a bunch of libraries (.dll) and a bit of extra stuff to
kick start things that required to run .NET apps.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/netstart/html/sdk_netstart.asp

 

[Stan Blazejewski]

So, correct me if I'm wrong, .NET framework is sort of an interface between 3rd
party software & the 'Windows' environment without the programmer having to
'understand' the inner workings of 'Windows'.

You'll have to install this only if you want to use an application that
requires it.

It provides to .NET based applications easier, wider and unified access to
Windows capabilities.

--

Australia isn't "down under", it's "off to one side"!

(e-mail address removed)
www.cobracat.com (home of the Australian Cobra Catamaran)
http://groups.yahoo.com/group/cobra-cat/

 

[Michael.Suarez]

Certain programs require the .NET framework being installed in order to
run on your computer.

Even though your computer works fine without it, you should install it
because it does nothing to harm your computer, and if you ever happen
to download a program requiring the .NET framework, you will need it.

Basically, programs that require the .NET framework are ones that were
built using it's functionality... specifically programs built using
Visual Studio .NET.

 

[Patrice]

Yes, for example you can create a Windows service by "inheriting" from a
..NET "class" that already knows how to interact with Windows. What's left is
just to implement what is done when the service starts or stops etc... but
the low level job is already done.

Basically .NET provides an object oriented view of the underlying Windows
capabilities...