(2010-06-28) dotNET Verification Tool
Posted by Jorge on 2010-06-28
FIM 2010 and a lot of other apps use some kind of version of .NET Framework. If you want to check the health and status of the .NET Framework version(s) you have installed, then you can use the .NET Framework Verification Tool.
.NET Framework Setup Verification Tool User’s Guide
This .NET Framework setup verification tool is designed to automatically perform a set of steps to verify the installation state of one or more versions of the .NET Framework on a computer. It will verify the presence of files, directories, registry keys and values for the .NET Framework. It will also verify that simple applications that use the .NET Framework can be run correctly.
The .NET Framework setup verification tool is available for download at the following locations:
REMARK: The .zip file that contains the tool also contains a file named history.txt that lists when the most recent version of the tool was published and what changes have been made to the tool over time.
The .NET Framework setup verification tool supports removing the following products:
- .NET Framework 1.0
- .NET Framework 1.1
- .NET Framework 1.1 SP1
- .NET Framework 2.0
- .NET Framework 2.0 SP1
- .NET Framework 2.0 SP2
- .NET Framework 3.0
- .NET Framework 3.0 SP1
- .NET Framework 3.0 SP2
- .NET Framework 3.5
- .NET Framework 3.5 SP1
- .NET Framework 4 Client
- .NET Framework 4 Full
By default, the .NET Framework setup verification tool will only list versions of the .NET Framework that it detects are installed on the computer that it is being run on. As a result, the tool will not list all of the above versions of the .NET Framework. This product filtering can be overridden by running the .NET Framework setup verification tool with the following command line switch:
–> netfx_setupverifier.exe /q:a /c:"setupverifier.exe /a"
Silent installation mode
The .NET Framework setup verification tool supports running in silent mode. In this mode, the tool will run without showing any UI, and the user must pass in a version of the .NET Framework to verify as a command line parameter. To run in silent mode, you need to download the verification tool .zip file, extract the file netfx_setupverifier.exe from the .zip file, and then run it using syntax like the following:
–> netfx_setupverifier.exe /q:a /c:"setupverifier.exe /p <name of product to verify>"
The value that you pass with the /p switch to replace <name of product to verify> in this example must exactly match one of the products listed in the Supported products section above. For example, if you would like to run the tool in silent mode and verify the install state of the .NET Framework 2.0, you would use a command line like the following:
–> netfx_setupverifier.exe /q:a /c:"setupverifier.exe /p .NET Framework 2.0"
The cleanup tool can returns the following exit codes:
- 0 – cleanup completed successfully for the specified product
- 1 – the required file setupverifier.ini was not found in the same path as setupverifier.exe
- 2 – a product name was passed in that cannot be verified because it does not support installing on the OS that the tool is running on
- 3 – a product name was passed in that does not exist in setupverifier.ini
- 100 – verification failed for the specified product
- 1602 – verification was canceled
This verification tool creates 2 log files by default that can be used to determine what actions the tool is taking and what errors it encounters while verifying a product. The 2 log files are listed below, and they are created in the %temp% directory by default. Note that you can find the %temp% directory by clicking on the Windows start menu, choosing Run, typing %temp% and clicking OK to open the directory in Windows Explorer.
- %temp%setupverifier_main_*.txt – this log contains information about all actions taken during a verification tool session; it will include information about each resource that the tool attempts to verify for a chosen product and whether or not that resource was found on the system; this log tends to be fairly long, so errors will be logged with the prefix ****ERROR**** to make it easy to search and find them
- %temp%setupverifier_errors_*.txt – this log only contains information about any errors found during verification of a chosen product
- %temp%setupverifier_netfx20testapp_*.txt – this log contains error information for the .NET Framework test application that is run by the verification tool. This log will only be created if there is an error while running the test application.
A new pair of log files will be created each time the verification tool is launched. The date and time the tool is launched will be appended to the end of the log file names by default in place of the * in the names listed above. If you want to control the exact names used for the log files, you can use the following command line parameters:
- /l <filename> – specifies a name to replace the default value of setupverifier_main_*.txt for the main activity log for the verification tool
- /e <filename> – specifies a name to replace the default value of setupverifier_errors_*.txt for the error log for the verification tool
For example, the following command line will allow you to specify non-default names for both log files:
–> netfx_setupverifier.exe /q:a /c:"setupverifier.exe /l %temp%my_main_log.txt /e %temp%my_error_log.txt"
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always evaluate/test yourself before using/implementing this!
* DISCLAIMER: https://jorgequestforknowledge.wordpress.com/disclaimer/
############### Jorge’s Quest For Knowledge #############
######### http://JorgeQuestForKnowledge.wordpress.com/ ########