Windows Legacy OS forum

General discussion

.NET v 3.5 sp 1 dependencies on earlier versions of .NET

If you have .NET 2.0 sp 2 installed and you upgrade to .NET 3.5 sp 1, when done you'll still have .NET 2.0 sp 2 and .NET 3.0 installed.

Is it correct that the .NET 3.5 sp 1 requires the earlier versions of .NET?

In other words, don't uninstall them?

Discussion is locked
You are posting a reply to: .NET v 3.5 sp 1 dependencies on earlier versions of .NET
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: .NET v 3.5 sp 1 dependencies on earlier versions of .NET
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Collapse -
Each .NET stands on its own.

In reply to: .NET v 3.5 sp 1 dependencies on earlier versions of .NET

I author .NET apps. If I author an app for .NET 2.0 and you install .NET 3.5 then the app fails.

3.5 is not an upgrade to 2.0. How that explains it well enough. It's a shame Microsoft blew the updates and has not issued a new update to fix that locked assemblies problem.
Bob

Collapse -
what 3.5 sp 1 installs

In reply to: Each .NET stands on its own.

I installed v 3.5 sp 1 and it installed v 3.0 sp 2 and left installed v 2.0 sp 2, which refuses to uninstall.

I don't know much about .NET but that's what happened to me.

Collapse -
When .net refuses to uninstall

In reply to: what 3.5 sp 1 installs

We have to use that .NET CLEANUP Utility. I am not sure why after a decade such things continue to malfunction. Let's think simple here. .NET is a series of files and registry entries. Why can't Microsoft supply an uninstaller or updater that works without us hunting down other tools?
Bob

Collapse -
Because Microsoft is the spawn of ... well, you get the idea

In reply to: When .net refuses to uninstall

Really. Why ask why about Microsoft?

Collapse -
Exactly.

In reply to: Because Microsoft is the spawn of ... well, you get the idea

Hope you fix it soon. I've had to use the .NET CLEANUP tool some hundred times last month (maybe more if you count folk that I helped.
Bob

Popular Forums

icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

SMART HOME

This one tip will help you sleep better tonight

A few seconds are all you need to get a better night's rest.