What are the main components of the Microsoft Application Compatibility Toolkit (ACT)?
What will be an ideal response?
The main components of ACT include these tools:
* Application Compatibility Manager-This is the administrative console that you use to control the overall discovery, collection, analysis process for apps. This is the interface that you use to access information in the ACT database.
* Inventory-collector package-This package is deployed to desktop computer to identify the apps that are installed. The results of the inventory are written to centralized files shared.
* ACT Log Processing Service-This services processes the logs collected from desktop computers and stores the information in the ACT database.
* ACT database-A Microsoft SQL Server database that stores information collected from desktop computers. It also stores compatibility information about apps. The Windows 10 ADK includes SQL Server 2012 Express for this purpose.
* Microsoft Compatibility Exchange-A web service that provides compatibility information that can be used ACT and incorporated into the ACT database. This is how information shared by other companies is provided to you.
* Runtime-analysis package-This package is deployed to computers in your test environment to monitor compatibility when running apps. The Compatibility Monitor tool is included in the package for this purpose. You can also use Compatibility Monitor to send a compatibility database to Microsoft.
You might also like to view...
Which of the following is the best file system to use in Windows?
A. FAT32 B. FAT C. NTFS D. FAT16
Write a program to solve the Towers of Hanoi problem. Use a recursive function with four parameters:
a) The number of disks to be moved b) The peg on which these disks are initially threaded c) The peg to which this stack of disks is to be moved d) The peg to be used as a temporary holding area Every budding computer scientist must grapple with certain classic prob- lems. The Towers of Hanoi (see Fig. 4.23) is one of the most famous of these. Legend has it that, in a temple in the Far East, priests are attempting to move a stack of disks from one peg to another. The initial stack had 64 disks threaded onto one peg and arranged from bottom to top by decreasing size. The priests are attempting to move the stack from this peg to a second peg, under the constraints that exactly one disk is moved at a time and that at no time may a larger disk be placed above a smaller disk. A third peg is available for holding disks temporarily. Supposedly, the world will end when the priests complete their task, so there is little incentive for us to facilitate their efforts. Let us assume that the priests are attempting to move the disks from peg 1 to peg 3. We wish todevelop an algorithm that will print the precise sequence of peg-to-peg disk transfers. If we were to approach this problem with conventional methods, we would rapidly find ourselves hopelessly knotted up in managing the disks. Instead, if we attack the problem with recursion in mind, it immediately becomes tractable. Moving n disks can be viewed in terms of moving only n - 1 disks (hence, the recursion), as follows: a) Move n - 1 disks from peg 1 to peg 2, using peg 3 as a temporary holding area. b) Move the last disk (the largest) from peg 1 to peg 3. c) Move the n - 1 disks from peg 2 to peg 3, using peg 1 as a temporary holding area. The process ends when the last task involves moving n = 1 disk, i.e., the base case. This is accomplished by trivially moving the disk without the need for a temporary holding area. Your program should print the precise instructions it will take to move the disks from the starting peg to the destination peg. For example, to move a stack of three disks from peg 1 to peg 3, your program should print the following series of moves: 1 ? 3 (This means move one disk from peg 1 to peg 3.) 1 ? 2 3 ? 2 1 ? 3 2 ? 1 2? 3 1? 3