.NET FRAMEWORK SETUP VERIFICATION TOOL USER'S GUIDE The latest version of this user's guide can be found

at http://blogs.msdn.com/as tebner/pages/8999004.aspx. ----------------------------INTRODUCTION ----------------------------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 comput er. 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. ----------------------------DOWNLOAD LOCATIONS ----------------------------The .NET Framework setup verification tool is available for download at the foll owing locations: http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog%7C_Tools/netfx%7C_s etupverifier%7C_new.zip http://blogs.msdn.com/astebner/attachment/8999004.ashx 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 ov er time. ----------------------------SUPPORTED PRODUCTS ----------------------------The .NET Framework setup verification tool supports verifying the following prod ucts: .NET .NET .NET .NET .NET .NET .NET .NET .NET .NET .NET .NET .NET Framework Framework Framework Framework Framework Framework Framework Framework Framework Framework Framework Framework Framework 1.0 1.1 1.1 SP1 2.0 2.0 SP1 2.0 SP2 3.0 3.0 SP1 3.0 SP2 3.5 3.5 SP1 4 Client 4 Full

By default, the .NET Framework setup verification tool will only list versions o f 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 over

verification failed for the specified product 1602 .NET Fram ework to verify as a command line parameter.N ET Framework 2.zip file.exe /q:a /c:"setupverifier. For example.NET Framework 2. and the user must pass in a version of the .ini was not found in the same path as set upverifier. you need to download the verific ation tool .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 .exe /a" ----------------------------SILENT MODE ----------------------------The .exe from the .zip file.exe /p . To run in silent mode.ridden by running the .0" ----------------------------EXIT CODES ----------------------------The verification tool can returns the following exit codes: 0 verification completed successfully for the specified product 1 the required file setupverifier. if you would like to run the tool in silent mode and verify the install state of the .NET Framework setup verification tool with the following command line switch: netfx_setupverifier.ini 100 . In this mode.NET Framework setup verification tool supports running in silent mode. Note that you can find the %temp% directory by clicking on the Windows start menu.exe /q:a /c:"setupverifier. extract the file netfx_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. choosing Run.exe /q:a /c:"setupverifier. the tool will run without showing any UI. The 2 log fi les are listed below. typing %temp% and clicking OK to open the directory in .verification was canceled ----------------------------LOG FILES ----------------------------This verification tool creates 2 log files by default that can be used to determ ine what actions the tool is taking and what errors it encounters while verifying a product. and they are created in the %temp% directory by default. and then run it usi ng syntax like the following: netfx_setupverifier.0. you would use a command line like the following: netfx_setupverifier.

this log tends to be fair ly long.txt" . The date and time the tool is launched will be appended to the end of the log file names by default in plac e of the * in the names listed above.specifies a name to replace the default value of setupverifier_m ain_*.exe /l %temp%\my_main_log.this log contains information about all action s taken during a verification tool session. %temp%\setupverifier_main_*.txt /e %temp%\my_error_log.this log only contains information about any errors found during verification of a chosen product A new pair of log files will be created each time the verification tool is launc hed.Windows Explorer. so errors will be logged with the prefix ****ERROR**** to make it easy to search and find them %temp%\setupverifier_errors_*.specifies a name to replace the default value of setupverifier_e rrors_*.txt .txt for the error log for the verification tool For example. you can u se the following command line parameters: /l <filename> . If you want to control the exact names used for the log files. the following command line will allow you to specify non-default na mes for both log files: netfx_setupverifier.exe /q:a /c:"setupverifier.txt .txt for the main activity log for the verification tool /e <filename> . it will include information abou t each resource that the tool attempts to verify for a chosen product and wh ether or not that resource was found on the system.

Sign up to vote on this title
UsefulNot useful