Windows 8 : A step backwards for the .net famework?


Recommended Posts

I?ve never been a fan of the .net framework. It always takes forever to install and back in the XP days most machines didn?t have it. Well .net still takes forever to install but in Windows 7 anything that required.net ?Just workes?.

Now in Windows 8 all of that is changing again. Last night I went to open up ?Patchmypc? on my windows 8 machine. I was prompted that I did not have 2.0 or 3.5 and it gave me the option to install it. So I clicked install and 5 mins later it had downloaded and installed and I could use ?Patchmypc?. This was never an issue on windows 7 it just worked.

Now I?m becoming annoyed with .net all over again.

I?ve never been a fan of the .net framework. It always takes forever to install and back in the XP days most machines didn?t have it. Well .net still takes forever to install but in Windows 7 anything that required.net ?Just workes?.

Now in Windows 8 all of that is changing again. Last night I went to open up ?Patchmypc? on my windows 8 machine. I was prompted that I did not have 2.0 or 3.5 and it gave me the option to install it. So I clicked install and 5 mins later it had downloaded and installed and I could use ?Patchmypc?. This was never an issue on windows 7 it just worked.

Now I?m becoming annoyed with .net all over again.

I?ve never been a fan of the .net framework. It always takes forever to install and back in the XP days most machines didn?t have it. Well .net still takes forever to install but in Windows 7 anything that required.net ?Just workes?.

Now in Windows 8 all of that is changing again. Last night I went to open up ?Patchmypc? on my windows 8 machine. I was prompted that I did not have 2.0 or 3.5 and it gave me the option to install it. So I clicked install and 5 mins later it had downloaded and installed and I could use ?Patchmypc?. This was never an issue on windows 7 it just worked.

Now I?m becoming annoyed with .net all over again.

I don't know WTF you're talking about because .Net never "just worked" on 7.... can't tell you how much of a huge pain in the ass .net is for when you're trying to deploy applications, not matter what OS they're running.

I don't know WTF you're talking about because .Net never "just worked" on 7.... can't tell you how much of a huge pain in the ass .net is for when you're trying to deploy applications, not matter what OS they're running.

Well in the case of applications that required dotnet 2.0 like patchmypc and CDburner XP they always "just worked". Now they don't anymore.

Every version of Windows ships with the newest version of the framework. Windows 8 ships with version 4.5. Most apps should run against it regardless of what they were written for, but if the app author specified that a specific version was required (i.e. 2.0-3.5 in your case) then it will be downloaded and installed on-demand. Including this by default would have taken up significant disk space when most people will never use it. Even in cases like yours, this step will go away if the app author removes the version requirement from their app, or builds it against .NET 4.x.

  • Like 2

I?ve never been a fan of the .net framework. It always takes forever to install and back in the XP days most machines didn?t have it. Well .net still takes forever to install but in Windows 7 anything that required.net ?Just workes?.

Now in Windows 8 all of that is changing again. Last night I went to open up ?Patchmypc? on my windows 8 machine. I was prompted that I did not have 2.0 or 3.5 and it gave me the option to install it. So I clicked install and 5 mins later it had downloaded and installed and I could use ?Patchmypc?. This was never an issue on windows 7 it just worked.

Now I?m becoming annoyed with .net all over again.

Windows 7 includes the .NET 3.5 runtime (which has support for .NET 3.5, 3.0 and 2.0)

Windows 8 includes the .NET 4.5 runtime (which has support for .NET 4.5 and 4.0)

As you stated in your post, if you have an app built with < .NET 4.0 you simply have to click "yes" and it installs the framework with no problems. What is there to be 'annoyed' about?

Windows 7 includes the .NET 3.5 runtime (which has support for .NET 3.5, 3.0 and 2.0)

Windows 8 includes the .NET 4.5 runtime (which has support for .NET 4.5 and 4.0)

As you stated in your post, if you have an app built with < .NET 4.0 you simply have to click "yes" and it installs the framework with no problems. What is there to be 'annoyed' about?

Because of how long .net takes to install. Do you know .net 4 can sometimes take more than 5 minutes to install?

Cant you spare 5 mins? It's not like you have to install it every day ;)

In the case of patchmypc I run it on every machine I work on. (though in this case he could fix it in his code)

Not crying, just saying never was an issue on windows 7.

That's because .NET Framework 3.5 was the latest version 3 whole years ago, when Windows 7 was released. You can't blame Microsoft for this, when the developer has had over 2 years to update their app (since .NET Framework 4.0 was released). It isn't Microsoft's fault that his app "just worked" on Windows 7 and it doesn't on Windows 8; it's up to the developer to ensure their app works. Microsoft doesn't update developers' apps for them, and you can't expect them to.

  • Like 2

Not crying, just saying never was an issue on windows 7.

Actually the exact same issue existed on Windows 7 for apps which required .NET 1.x. The main thing that's changed in Windows 8 is that instead of the older versions being on the install disc, the bits are now downloaded from WU. This saves space on install discs / OEM images, and ensures you always get the latest version (versus having to install the on-disc one, then download the latest SP and security updates).

That's because .NET Framework 3.5 was the latest version 3 whole years ago, when Windows 7 was released. You can't blame Microsoft for this, when the developer has had over 2 years to update his app (since .NET Framework 4.0 was released). It isn't Microsoft's fault that his app "just worked" on Windows 7 and it doesn't on Windows 8; it's up to the developer to ensure their app works. Microsoft doesn't update developers' apps for them, and you can't expect them to.

Precisely.

As I myself have pointed out, whenever any application need an older version of *any* runtime (.NET, DirectX, VC++, etc.) Windows 8 goes and fetches it if it's not already installed - and it only has to do it *once*. I have two games (NFS: Hot Pursuit 2010 and DCUO) that require .NET 3.x; which one triggers the fetch depends on which order I install them in. However, it's ONLY triggered once. That means that by the time Office 2013 Preview gets installed (typically the last application or suite TO get installed) my runtimes have been *caught up*.

Well at least it doesn't do a cryptic error or fail silently. I hate when that happens - Do not have Visual C++ runtime 2005 - well I am going to silently fail on you and laugh at your almost futile attempts at searching the net for a solution.

This "you need old version of .Net" is properly done IMO. Fast and simple.

It's definitely a step forward.

Even better is that you can use the Windows Deployment tools to have Windows auto install it if you want, and you can enable it from "Add Windows Features".

Also, my install took about 2 minutes of downloading on terrible net and about 1.5 minutes of install. It might be due to my SSD, but I never remember .net installing that slowly..

EDIT:: The only step back is that IIS automatically uses 4.x as the framework target regardless of what you specify. Thus certain configs (like default document/connection info) bomb out if you are using an older frame work in your build.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Owing to the nature of Windows feature enablement updates, it was distributed over Windows Update services as a complete system upgrade rather than as an ordinary cumulative update
    • Microsoft confirms Windows 11 26H2, urges IT admins to prepare for release by Usama Jawad Windows 11 typically follows an annual update cycle, but Microsoft recently broke that tradition a bit by releasing a "26H1" version in the first half of this year as a "scoped" build for select new silicon PCs only. This version was not available for customers using 24H2 and 25H2 builds, as Microsoft is busy preparing version 26H2 for them, confirmed officially for the first time. In a Windows IT Pro blog, Microsoft has urged IT admins to prepare for the upcoming release of Windows 11 version 26H2. The company has confirmed that this will be a small enablement package (eKB) that will simply light up certain disabled features that are already present in the operating system's code base. This means that the "refined" Windows update and deployment experience will be simpler and quicker, with minimal disruptions, as the feature update will simply toggle a few flags rather than performing a complete replacement. Microsoft has explained that this is all possible because the standard Windows 11 releases share the same servicing branch and hence, the same source code. However, this also means that Windows 11 26H1 users won't be able to upgrade to 26H2 as that is a different branch, but this is something we have known for a while now. Similar to previous annual feature updates, Windows 11 26H2 will offer the following support cycles: 24 months of support for Home, Pro, Pro EDU, and Pro for Workstations editions 36 months of support for Enterprise, Education, IoT Enterprise, and Enterprise Multi-session editions Microsoft has not confirmed a concrete release date for Windows 11 26H2, but noted that it is "coming soon". If we go by the ongoing release cadence, we can expect it to begin rolling out in early October 2026. As such, IT admins have been encouraged to begin validating Windows Insider releases in the Experimental Channel, plan rollout rings, and strategize the utilization of their existing deployment tools.
    • Windows 11 gets new audio improvements in the latest builds by Taras Buria Today's Experimental builds (26H1 and Future Platforms, formerly Canary) pack several audio-related improvements. If your device is enrolled in the Experimental Channel (26H1), you can download build 28120.2315, while those in the Future Platforms version have build 29613.1000 to try. Here is what is new in build 29613.1000: [Audio] Following up on our previous improvements, we’re making some more adjustments to Settings > System > Sounds based on your feedback. Namely, we’ve updated the “All sound devices” page so: You now have the ability to change default devices from this page. Each of the devices displayed on this page now has a little volume meter next to it to show if there is audio actively playing. We’ve adjusted the page design slightly so now you can filter whether you’re viewing input or output devices. We’ve added toggles so you can choose if you want to hide or show disabled, disconnected, and unplugged devices on this page. We’ve also updated the input and output audio properties page for devices in Settings to now include jack information for those that need it. And here is the changelog for build 28120.2315: This update includes a small number of minor bug fixes and improvements. [Accessibility] This update improves caption style responsiveness by redrawing captions immediately for caption style changes. If no current caption is visible, a sample caption string is displayed. [Audio] This update improves the reliability of the inbox HD Audio driver. You can find the official release notes for build 28120.2315 here and for build 29613.1000 here.
    • I agree with what I think you are saying, just not in the way you are saying it. Like any tool, the amount it represents your work is perorational to the effort you put into it. It is similar to why 2nd grade math students learning to add and subtract are not allowed to use calculators, but a high-school calculous student is. For the 2nd grader, that tool would completely replace the work they are doing, for the calculous student the same tool allows them to work far more effectively while in no way replacing their effort or knowable. If you spend 30 seconds writing a prompt, then the image that comes out is no more "yours" than if you found the same image with a Google Image search. However, many of these generative tools also support highly iterative processes that allow back and forth, and merging generated images with photos or human created images. I am sure you would agree that a human spending hours of time working on a project, even if AI was involved in the process, still reflects that human's work.
  • Recent Achievements

    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      575
    2. 2
      +Edouard
      189
    3. 3
      Michael Scrip
      79
    4. 4
      PsYcHoKiLLa
      78
    5. 5
      neufuse
      72
  • Tell a friend

    Love Neowin? Tell a friend!