View Single Post
  #10  
Old January 29th 09, 07:31 PM posted to microsoft.public.windowsxp.newusers
Twayne[_2_]
external usenet poster
 
Posts: 4,276
Default Microsoft .Net Framework

Thanks JS. You wrote Each version of .NET
is usually
installed along with the application that
requires it.
I distinctly recall installing Microsoft. Net
Framework
V2 and others as an optional download from the
Microsoft
update site. Thought at the time it may be
useful. I'm
reasonably sure that this was overkill and now
I'm
looking to uninstalling redundant software just
as a
tidying up exercise. The problem is I don't
know if any
subsequently installed software may need any of
the
versions of .NET which is why (coming back to my
original
question) I was looking at identifying what may
need
them. One way would be to uninstall all
versions of .NET
and see what doesn't work but that's a bit
extreme. Is
there an easy way?
Bill Ridgeway

"JS" @ wrote in message
...
If you have an application that uses/needs .NET
1.1 then
2.0 and 3.0 are not
to be considered supersets or replacements for
.NET 1.x
So if you where to delete version 1.1 then
there is a
good chance the application that requires .NET
1.1 will fail. The
same is true for later
versions.

Each version of .NET is usually installed along
with the
application that requires it, so if you have
all three
or four versions, then chances are that
somewhere along
the way you installed at a minimum 3 or 4
applications,
with each of those applications requiring and
installing
it's own version of .NET --
JS
http://www.pagestart.com


"Bill Ridgeway"
wrote in
message
...
I have installed -
Microsoft .Net Framework 1.1
Microsoft .Net Framework 2.0 Service Pack 2
Microsoft .Net Framework 3.0 Service Pack 2
Microsoft .Net Framework 3.5 Service Pack 1

I am looking at uninstalling redundant
software and I
don't know what they do or whether or not I
actually
need them. Any advice please? Bill Ridgeway



Safest way, IMO:

Try just renaming the filenames to something like
fname_OLD.whatever the TLD was. e.g., just add
OLD or something easy to spot to the end or
beginning of the filename.

Then go about your daily work, or exercise
everything you can think of on your machine to see
if it works OK. If a program fails that needs the
framework, it will almost certainly tell you so in
the error message, and usually also details which
one it is that you need.

If nothing shows up after a week or so, then
delete them, or if you're a little paranoid, copy
them to a CD/DVD and then delete them. That way
you can get them back easily if they're on
CD/DVDs, just in case you missed what it is that
needs them.

HTH

Twayne


Ads