Updated sample code that can detect the .NET Framework 3.5

Interesting Finds: November 30, 2007

Jason Haley — Fri, 30 Nov 2007 18:03:17 GMT

Powershell script to get installed versions of the .NET Framework

Meta-Code — Fri, 30 Nov 2007 21:04:13 GMT

Powershell script to get installed versions of the .NET Framework

re: Updated sample code that can detect the .NET Framework 3.5

someone — Fri, 30 Nov 2007 22:15:25 GMT

Hey I have a different question. What happened to the update.exe switches like "/nobackup", "/forcerestart", "/promptrestart" and "/overwriteoem" etc etc. There were so many switches for Update.exe. Are they all removed in Windows Vista? Both pkgmgr.exe and wusa.exe have very limited number of switches.

re: Updated sample code that can detect the .NET Framework 3.5

astebner — Fri, 30 Nov 2007 22:49:34 GMT

Hi Someone - Update.exe is only used on OS's before Windows Vista. There are a different set of switches, and it looks like not all of the ones offered by update.exe are available from pkgmgr or wusa. I'm not sure why there is such a big discrepancy, but in at least some of the cases, the command line switches are not relevant anymore because the Windows Vista OS is installed and serviced using an entirely new installation technology.

There is more information about wusa at http://support.microsoft.com/kb/934307, included supported command line switches. Wusa is essentially a wrapper around some of the same things that pkgmgr can do. Pkgmgr can be run with /? to see the syntax of the command line switches, but using it directly requires some specific knowledge about how Windows Vista OS components/packages are composed and it isn't advised to try to run it directly in most cases.

re: Updated sample code that can detect the .NET Framework 3.5

someone — Sat, 01 Dec 2007 16:37:47 GMT

I don't see how particularly /forcerestart, /warnrestart, /promptrestart, /overwriteoem, /nobackup, /forceappsclose are all not relevant anymore. Also, the new servicing stack seems to have introduced additional time before, while and after applying any update/hotfix instead of reducing/eliminating it. After every small update/hotfix which is today frequently being delivered over Windows Update, I see the "Configuring updates...please wait" screen for quite some time before logon. Can you blog about what exactly Windows Vista is doing during that time and whether a user can do anything to speed it up? In fact I cannot see how the entirely new servicing stack improves upon the older one except that now its possible to service the image "offline". According to http://technet2.microsoft.com/WindowsVista/en/library/77bd6146-1dae-4f3f-b172-4aa5fc876bdc1033.mspx, package manager does not seem to backup files to %Windir% like Update.exe. What happens then if a user does SFC.EXE and original unpatched files are restored from the Vista DVD? Usually pre-Vista, SFC restored updated/patched files from the backed up location. How is this handled in Vista if no backup is made before patching?

re: Updated sample code that can detect the .NET Framework 3.5

astebner — Mon, 03 Dec 2007 08:06:17 GMT

Hi Someone - I didn't work on the team that created the Vista servicing stack, so I can't answer all of your questions unfortunately. Windows Vista stores a copy of each OS file, including each version installed by patches, in %windir%\winsxs, and it is not possible to cause Windows Vista to downgrade to unpatched files using sfc.exe without installing the hotfix that contains the newer versions of the files. Because of that, I don't think the /nobackup or /overwriteoem switches make sense any more. I'm not sure about some of the other switches.

There are some performance issues with the servicing stack that are being worked on for future hotfixes or service packs of Windows Vista. There isn't really anything the user can do to speed up the "configuring updates" dialog - that time is being spent by the servicing stack configuring the hotfixes on the system.

The Daily Find #9 - TechToolBlog

The Daily Find #9 - TechToolBlog — Mon, 03 Dec 2007 19:05:54 GMT

PingBack from http://www.techtoolblog.com/archives/the-daily-find-9

re: Updated sample code that can detect the .NET Framework 3.5

dalkema — Mon, 10 Dec 2007 21:25:44 GMT

Too bad there wasn't a way to query WMI for a list of runtimes.

re: Updated sample code that can detect the .NET Framework 3.5

astebner — Mon, 10 Dec 2007 21:37:28 GMT

Hi Dalkema - There are not any pre-built WMI queries to detect the .NET Framework version. However, the versions of the .NET Framework can be detected by looking up registry values, which I think is a fairly straightforward way of detecting product install state. Are there some advantages gained by supporting WMI queries for this type of detection as opposed to registry detection? I am asking because I don't have much experience using WMI.

.NET Framework 3.5 deployment guides have been published on MSDN

Aaron Stebner's WebLog — Sat, 26 Jan 2008 04:05:53 GMT

The official deployment guides for system administrators and application developers have been posted

.NET Framework 3.5 deployment guides have been published on MSDN

Noticias externas — Sat, 26 Jan 2008 04:20:41 GMT

The official deployment guides for system administrators and application developers have been posted

Prerequisites for running XNA Framework 2.0-based games on Windows

Aaron Stebner's WebLog — Sat, 01 Mar 2008 05:01:34 GMT

There are a several prerequisite dependencies that must be satisfied on a Windows system that does not

Prerequisites for running XNA Framework 2.0-based games on Windows

Noticias externas — Sat, 01 Mar 2008 05:25:54 GMT

There are a several prerequisite dependencies that must be satisfied on a Windows system that does not

How to automate the install of the .NET Framework 3.0 OS component on Windows Vista and Windows Server 2008

Aaron Stebner's WebLog — Sat, 05 Apr 2008 04:19:34 GMT

Windows Vista and Windows Server 2008 include the .NET Framework 2.0 and 3.0 as OS components. However,

Unified .NET Framework Troubleshooting Guide

Aaron Stebner's WebLog — Thu, 05 Jun 2008 20:18:14 GMT

Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework

Mailbag: How can I detect the presence of the .NET Framework 2.0 or later in my MSI-based installer?

Aaron Stebner's WebLog — Tue, 08 Jul 2008 03:44:46 GMT

Question: I am creating an application that is built on the .NET Framework 2.0, and I am attempting to

The Dark Side of XNA » Railgun Setup Build

The Dark Side of XNA » Railgun Setup Build — Sun, 17 Aug 2008 23:53:56 GMT

PingBack from http://www.darklock.com/xna/?p=53

Mailbag: How to create a Visual Studio project to compile the sample .NET Framework detection code

Aaron Stebner's WebLog — Tue, 19 Aug 2008 03:57:55 GMT

Question: I have downloaded both versions of the sample .NET Framework version detection code (described

Links to information about .NET Framework package sizes and web-based detection logic

Aaron Stebner's WebLog — Wed, 24 Dec 2008 00:21:16 GMT

Back when the .NET Framework 3.5 shipped, I posted a brief explanation about the size and contents of

Presenza Framework 3.5 ed eventuale installazione | hilpers

Presenza Framework 3.5 ed eventuale installazione | hilpers — Sun, 18 Jan 2009 16:38:25 GMT

PingBack from http://www.hilpers.it/2760061-presenza-framework-3-5-ed

Wade’s Word » Find Dot Net Frameworks on Win32 PC using C++

Wade’s Word » Find Dot Net Frameworks on Win32 PC using C++ — Wed, 21 Jan 2009 17:50:08 GMT

PingBack from http://wadesword.org/Blog/?p=289

How to create a Visual Studio project to compile the sample .NET Framework detection code

Aaron Stebner's WebLog — Sun, 01 Feb 2009 07:59:16 GMT

I posted some sample code a while back to demonstrate how to detect whether or not each version of the

Updated .NET Framework setup verification tool with product filtering is now available

Aaron Stebner's WebLog — Tue, 24 Feb 2009 06:18:34 GMT

Over the weekend, I posted an updated version of the .NET Framework setup verification tool that contains