Internal Build Process

From DevRiot for VS .Net Documentation

RIOT keeps his own build process because if the way it works. Once Visual Studio finishes a build DevRiot checks if it was successful.

If it wasn't RIOT does nothing, but if the build was successful, RIOT internal build process begins it verifies that the information given to it is still valid. It walks the internal build trees and it compares their contents against the latest code pruning out of it build trees whatever methods, fields are no longer available. But it does NOT remove them from storage.

So it is possible to recuperate those tests if changes are reverted.

In its rebuilding efforts, RIOT creates daisy chains of related assemblies within the current Visual Studio solution. Under some circumstances deadlock may occur.

NOTE: Visual Studio is a product and/or trademark of Microsoft Corporation.