Extending Isolator Configuration

Typemock Isolator supports 3 extension types that can boost performance or immediately solve issues otherwise requiring to await a new version.
Before every test run Isolator tries to import the configuration files(.dat) from the installation directory.

When using AutoDeploy feature, place configuration files(.dat) in the AutoDeploy directory that you created and check them into source control.

The extensions are listed below:

Configuration File	Description
blacklist.dat	Add list of assemblies to exclude them from mocking. Note to write only names without file extension. This can boost mocking performance.
exclude.dat	Add list of assemblies to exclude them from mocking mscorlib. For example, adding MyAssembly.dll below will disable Isolator for mocking calls to classes located in mscorlib.dll for MyAssembly.dll For supported mscorlib types see here.
knownRunners.dat	Add list of custom test runner's assembly (exe or dll) to enable mocking.

Add one value per line.

Put # in the beginning of a line to comment it.

Examples:

Example configuration files are available as part of the installation in <installDir>\Examples\ExtendedConfigurationExamples.

Example1: Add support for a custom test runner - MyUnitTestRunner.exe

Open installation directory (default is <installDir>\BuildScripts\AutoDeploy)
Create a new text file and rename it to "knownRunners.dat"
Add the name of your test runner "MyUnitTestRunner.exe" (for Isolator to support more runners, add each in a separate line)
Save and close "knownRunners.dat"
Run Isolator test assemblies with your runner

Inform Typemock support of the new runner so it might be supported out of the box in future versions.