automate .Net setup verification

[GoogleCodeExporter]

Focht sent me this when I asked him about the recent .Net conflicts changeset. 
Adding it to the tracker so it doesn't get lost.
=============================================
The testing can be a bit automated .. at least the outer installer, the inner 
with autoit.

http://www.serverexception.com/net-framework-verification/

--- snip ---
$ wine ./netfx_setupverifier.exe /q:a /c:"setupverifier2.exe /a"
--- snip ---

The main app 'setupverifier2.exe' could be automated using small autoit script 
that just clicks "verify now" for currently detected framework and then "exit".
For specific version check you need to automate selection from dropdown (list 
index = constant) and then verify + exit

---quote ---

Exit codes

The verification tool can returns the following exit codes:
•0 - verification 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  - specifies a name to replace the default value of 
setupverifier_main_*.txt for the main activity log for the verification tool
•/e  - 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:"setupverifier2.exe /l %temp%\my_main_log.txt 
/e %temp%\my_error_log.txt"

--- quote ---

=============================================

I'm thinking either a helper function at the end of each .Net verb 
(w_verfiy_dotnet $dotnet_version).

The question is if we want to automatically verify every install (in silent 
mode, easy enough), but for non-interactive, the user may be confused when 
given the dialog).

Thoughts?

Original issue reported on code.google.com by austinenglish@gmail.com on 4 Mar 2014 at 8:31

[GoogleCodeExporter]

We could add a --enable-checks option to winetricks initially
until we are sure the option is robust and non-annoying, I suppose.

Original comment by daniel.r...@gmail.com on 4 Mar 2014 at 8:41

[GoogleCodeExporter]

I went with --verify. It's optional, not default. It's also enabled by 
winetricks-test (by the new test_dotnet feature) for all .Net verbs.

Fixed by r1163/r1165, et al.

Original comment by austinenglish@gmail.com on 26 Mar 2014 at 11:41

• Changed state: Fixed