Updated .NET Framework setup verification tool with product filtering is now available
Over the weekend, I posted an updated version of the .NET Framework setup verification tool that contains a few behavior changes that I wanted to describe here. I have also updated the .NET Framework Setup Verification Tool User's Guide to reflect these changes, and you can find additional information and download links there as well.
Added product version filtering logic to the verification tool
Previously, the tool would allow you to choose to verify any version of the .NET Framework that it knows how to verify, even if that version was not actually installed on your system.
Now, the tool will use the logic in the .NET Framework sample detection code to detect which version(s) and service pack level(s) of the .NET Framework are installed, and it will only show version(s) on the system in the UI.
This logic will not apply if you run the tool in unattended or silent mode. Those modes will function just like before and will allow you to attempt to verify any supported version of the .NET Framework, even if it is not detected as being installed on the system.
Added a command line parameter to override the product filtering logic described above
In case there is any need to run the .NET Framework setup verification tool in UI mode and choose a version of the .NET Framework that is not installed, you can run the tool with the new /a switch and cause it to skip filtering and instead allow you to select any version of the .NET Framework to verify, even if it is not detected as being installed on the system.
Here is an example command line for the .NET Framework setup verification tool that will skip filtering:
netfx_setupverifier.exe /q:a /c:"setupverifier.exe /a"
Added an option to verify the .NET Framework 1.1 SP1
Previously, the .NET Framework setup verification tool only offered the ability to verify the .NET Framework 1.1, but did not verify anything related to 1.1 SP1.
Now, the tool includes the ability to verify the .NET Framework 1.1 and the .NET Framework 1.1 SP1. As described above, only the version and service pack level that is detected as being installed on the system will be listed in the UI for the tool.
Added better logging for registry values being verified
Previously, the .NET Framework setup verification tool did not list the registry root of the keys and values it verifies in the log files that it creates (for example, it would only list Software\Microsoft\.NETFramework\Policy but not list HKEY_LOCAL_MACHINE).
Now, the tool lists the full path to the registry keys and values that it verifies in the log files that it creates.
Comments
Anonymous
March 06, 2009
PingBack from http://www.brunorodrigues.pro.br/dev/?p=233Anonymous
March 17, 2015
dumanski@bell.net I know you have explained how to fix this problem (every time I start my computer I get a message that "Microsoft.NET framework version 2.0 needs to be installed) I unfortunately every time I try to install it says " program not compatible with your computer x32. I then install the same program for x64. It comes back and says it's already installed. So what do I do with the warning window, which pops up every time my computer stats up ?Anonymous
March 18, 2015
Hi Wayne Dumanski - I wrote a post about troubleshooting this type of error a while back. Can you take a look at blogs.msdn.com/.../10288684.aspx and see if the steps there help you solve this issue?