1*b1cdbd2cSJim JagielskiThis test is for Windows only! 2*b1cdbd2cSJim Jagielski 3*b1cdbd2cSJim JagielskiThe cli test uses .NET assemblies: 4*b1cdbd2cSJim Jagielskicli_types.dll, 5*b1cdbd2cSJim Jagielskicli_basetypes.dll, 6*b1cdbd2cSJim Jagielskicli_ure.dll, 7*b1cdbd2cSJim Jagielskicli_cppuhelper.dll. 8*b1cdbd2cSJim Jagielski 9*b1cdbd2cSJim Jagielski 10*b1cdbd2cSJim JagielskiWhen an office is properly installed then these assemblies can be found in the 11*b1cdbd2cSJim Jagielskiglobal assebly cache (GAC), for example in c:\windows\assembly. 12*b1cdbd2cSJim Jagielski 13*b1cdbd2cSJim JagielskiWhen the test is run then the assemblies are used from the GAC. That is 14*b1cdbd2cSJim Jagielskione has to make sure that one has the respective office installed. 15*b1cdbd2cSJim Jagielski 16*b1cdbd2cSJim JagielskiThe test can also be run without an installed office. Then the assemblies are used 17*b1cdbd2cSJim Jagielskiwhich reside next to the executable. The testtools project copies the assemblies from 18*b1cdbd2cSJim Jagielskithe build environment into the wntmscixx\bin folder. 19*b1cdbd2cSJim Jagielski 20*b1cdbd2cSJim JagielskiHowever, if for some reason an assembly remains in the GAC than it is used no matter 21*b1cdbd2cSJim Jagielskiwhat. 22*b1cdbd2cSJim Jagielski 23*b1cdbd2cSJim Jagielski 24*b1cdbd2cSJim JagielskiThe qa test simply executes the cli_bridgetest_inprocess.exe. All console output is decarded. 25*b1cdbd2cSJim JagielskiWhen the test fails one should directly run that executable. Then one may see the cause 26*b1cdbd2cSJim Jagielskiof the failure in the console. 27