Thread: Net. Framework
View Single Post
  #10  
Old February 22nd 12, 07:36 AM posted to microsoft.public.windowsxp.general
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default Net. Framework

Bruce Hagen wrote:

Jeff T wrote ...

Do I need net framework? Are there any risks to uninstalling it?


.NET Framework is needed to run programs and no new version supersedes
another.

Just as an example, XP would never run without V: 1.1 and Turbo Tax
requires V: 3.5.


Since Windows XP was released in 2001 and .Net Framework in 2002, how
could Windows XP be dependent on Net Framework? When released, Windows
XP couldn't include any .NET libraries since they didn't exist yet. I
don't of anything in Windows XP, even with service packs, that requires
..Net other than perhaps ancilliary utilities. You can install Windows
XP gold edition with no updates and it runs as do non-.Net apps on it.

The OS isn't dependent on Net Framework. *Applications* that are
dependent on it. Net is a application development environment and
allows many programming languages (well, Microsoft's languages, that
is). It provides a coding environment along with more libraries (with
much larger scope than available for programming languages, like C++,
and comparable in scope to Java standard libraries). You don't have to
use it for app coding as it provides another coding layer to access the
OS but this requires more system resources that access the system API or
machine resources more directly.

Although .Net is commonly used as an abbreviation, the correct term is
..Net Framework. It is a framework in which to code applications. See:

http://en.wikipedia.org/wiki/Software_framework

Before .Net Framework, Microsoft provided the MFC (Microsoft Foundation
Class) library to assist C++ developers in application development.
Mozilla has theirs, there's Netbeans, Eclipse, and many others. Adding
a framework assisted coders but can add to code bloat. The incorporated
libraries include methods that the coder may never exercise.
Ads