.NET Framework

[paoloricardo]

In my Add/Remove Programs list I have the following:

..NET Framework 1.1
..NET Framework 1.1 Hotfix
..NET Framework 2.0 Service Pack 1
..NET Framework 3.0 Service Pack 1
..NET Framework 3.5

Do I need to keep all of these on my PC or just the latest (3.5)?

Thanks

 

[PA Bear [MS MVP]]

"If it ain't broke, don't fix it."

 

[Colin Barnhorst]

The versions of the .NET Framework are designed to be side-by-side and can
remain on your system together. Some programs address a specific version
(usually an error) so you should leave all installed.

Is there some issue you think this may be causing you?

 

[Ken Blake, MVP]

In my Add/Remove Programs list I have the following:

.NET Framework 1.1
.NET Framework 1.1 Hotfix
.NET Framework 2.0 Service Pack 1
.NET Framework 3.0 Service Pack 1
.NET Framework 3.5

Do I need to keep all of these on my PC or just the latest (3.5)?

All. Some programs require a specific version, and a newer one will
not work.

 

[Bill in Co.]

Or, if it ain't "broken", don't fix it.

"If it ain't broke, don't fix it."
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

 

[paoloricardo]

The versions of the .NET Framework are designed to be side-by-side and can
remain on your system together. Some programs address a specific version
(usually an error) so you should leave all installed.

Is there some issue you think this may be causing you?

OK, thanks

 

[paoloricardo]

All. Some programs require a specific version, and a newer one will
not work.

OK, wasn't sure about the need for each version.

 

[Uncle Grumpy]

Or, if it ain't "broken", don't fix it.

PA Bear's version was the correct one.

 

[Colin Barnhorst]

yw

OK, thanks

 

[Bill in Co.]

I think the English is better as I stated it. Eng 101, Grumpy?

 

[Kenneth]

Or, if it ain't "broken", don't fix it.

PA Bear [MS MVP] wrote:
"If it ain't broke, don't fix it."

PA Bear's version was the correct one.

I think the English is better as I stated it. Eng 101, Grumpy?

But what about the "ain't?"

The point is that the phrase is a colloquialism, and has
been around (grammatical errors and all) for many years.

All the best,

 

[Bob I]

Ain't gonna change da outcome!

I think the English is better as I stated it. Eng 101, Grumpy?

Or, if it ain't "broken", don't fix it.

PA Bear [MS MVP] wrote:

"If it ain't broke, don't fix it."

PA Bear's version was the correct one.

 

[Uncle Grumpy]

I think the English is better as I stated it. Eng 101, Grumpy?

**** English 101. The phrasing has ALWAYS used "broke".

 

[Bill in Co.]

Or, if it ain't "broken", don't fix it.

PA Bear [MS MVP] wrote:
"If it ain't broke, don't fix it."

PA Bear's version was the correct one.

I think the English is better as I stated it. Eng 101, Grumpy?

But what about the "ain't?"

LOL! Good one!

 

[Dale]

Probably a DUMB question....why do I need framework at all ? Just what does
it do ? (briefly)

I have had ver 1 to 3.5. I have uninstalled all of them.
Machine seems to run better without .net framework.

Windows Update wants to install an update, so apparently, something still
exists out there.

I suppose at some point, I will need to reinstall .net framework.

Colin Barnhorst wrote: Thank You Colin
The versions of the .NET Framework are designed to be side-by-side and can
remain on your system together. Some programs address a specific version
(usually an error) so you should leave all installed. (Thank You Colin)

I am gloing to assume (which I hate to do) that I should download and
install each version in following order.

..NET Framework 1.1
..NET Framework 1.1 Hotfix
..NET Framework 2.0 Service Pack 1
..NET Framework 3.0 Service Pack 1
..NET Framework 3

Could someone verify this for me ?

Thank You for you time.

 

[Timothy Daniels]

Probably a DUMB question....why do I need framework at all ?
Just what does it do ? (briefly)

It is the runtime environment for any app that uses .NET .
Among other things, it acts as the virtual machine for .NET
languages. In that respect, it's like the Java virtual machine.
You couldn't run Java without its virtual machine. You couldn't
run anything written in C# without the .NET Frameowork, either -
or anything written in C++.NET, or J#, or COBOL.NET, etc.
You'll find as time goes by, that more and more apps and utilities
will depend on .NET Framework being installed because .NET
allows for shorter development times, so you might as well have
..NET Framework installed

*TimDaniels*

 

[Ken Blake, MVP]

Probably a DUMB question....why do I need framework at all ? Just what does
it do ? (briefly)

..Net is a family of programming languages. The .net framework is a
corresponding run-time file for programs written using .net. You can't
run a .net program unless you have the corresponding .net framework
file available for it to use.

If you run such programs, you need the .net framework for them. If you
don't run them, you don't need them.

I have had ver 1 to 3.5. I have uninstalled all of them.

If you got away with doing that, then you don't run any programs that
need them. At some point in the future, you may find that you will
want to run such a program, and will have to reinstall one or more of
these.

Machine seems to run better without .net framework.

Nope, not possible. You might not have needed them, but there's no
downside to having them, and the computer can't run better without
them. What you did is like removing the ashtray from your car because
you don't smoke. That's' fine--you may not need the ashtray, but
removing it won't make the car run any better.

Windows Update wants to install an update, so apparently, something still
exists out there.

I suppose at some point, I will need to reinstall .net framework.

Since there are a lot of programs that need them, you will likely have
to reinstall one or more of them in the future.

 

[Bill in Co.]

.Net is a family of programming languages. The .net framework is a
corresponding run-time file for programs written using .net. You can't
run a .net program unless you have the corresponding .net framework
file available for it to use.

If you run such programs, you need the .net framework for them. If you
don't run them, you don't need them.




If you got away with doing that, then you don't run any programs that
need them. At some point in the future, you may find that you will
want to run such a program, and will have to reinstall one or more of
these.




Nope, not possible. You might not have needed them, but there's no
downside to having them, and the computer can't run better without
them. What you did is like removing the ashtray from your car because
you don't smoke. That's' fine--you may not need the ashtray, but
removing it won't make the car run any better.

Unless (possibly) it adds some resident running processes after windows
boots up. Does it do that, or does it ONLY do so when a program requiring
it is run? (I can't recall).

 

[Colin Barnhorst]

I don't think so. The runtime is just that.

.Net is a family of programming languages. The .net framework is a
corresponding run-time file for programs written using .net. You can't
run a .net program unless you have the corresponding .net framework
file available for it to use.

If you run such programs, you need the .net framework for them. If you
don't run them, you don't need them.




If you got away with doing that, then you don't run any programs that
need them. At some point in the future, you may find that you will
want to run such a program, and will have to reinstall one or more of
these.




Nope, not possible. You might not have needed them, but there's no
downside to having them, and the computer can't run better without
them. What you did is like removing the ashtray from your car because
you don't smoke. That's' fine--you may not need the ashtray, but
removing it won't make the car run any better.

Unless (possibly) it adds some resident running processes after windows
boots up. Does it do that, or does it ONLY do so when a program
requiring it is run? (I can't recall).

 

[Ken Blake, MVP]

Unless (possibly) it adds some resident running processes after windows
boots up. Does it do that,

Nope.


or does it ONLY do so when a program requiring
it is run?

Yes.