Not required: Visual Basic, Visual Studio or .NET Framework.
Certain project types are not officially supported. However, Project Analyzer may work with them. We don't guarantee the accuracy of the results, so use with care.
See also: Limitations and known bugs
The following files are required by Project Analyzer. Newer versions are generally compatible.
If you have Visual Basic 6.0, the following system files are already on your computer. If not, download and install the run-time library package ProA_VB60DLLs.zip. You may already have downloaded it with Project Analyzer. Run library setup to install the required run-times. If you have trouble with a system file, put it in your Windows\System32 directory and register it with regsvr32.exe. Run as Administrator if necessary.
| Filename | Size | Date | Time | Version | Details |
|---|---|---|---|---|---|
| MSVBVM60.DLL | 1,409,024 | 25/06/98 | 0:00 | v6.0.81.76 | |
| OLEAUT32.DLL | 598,288 | 02/06/98 | 18:24 | v2.30.4261.1 | |
| OLEPRO32.DLL | 164,112 | 02/06/98 | 18:24 | v5.0.4261.1 | |
| ASYCFILT.DLL | 147,728 | 02/06/98 | 18:24 | v2.30.4261.1 | |
| STDOLE2.TLB | 17,920 | 02/06/98 | 15:46 | v2.30.4261.1 | |
| COMCAT.DLL | 22,288 | 31/05/98 | 0:00 | v4.71.1460.1 | |
| MSCOMCTL.OCX | 1,062,704 | 26/06/98 | 0:00 | v6.0.81.77 | |
| TLBINF32.DLL | 153,600 | 18/06/98 | 0:00 | v1.1.81.69 | = v1.10.8169. For COM analysis. |
The following files are included with the Project Analyzer download. They should exist in your Project Analyzer directory. If you have trouble with one of these files, put it in your Project Analyzer directory and run Project Analyzer, which will automatically attempt to use it.
| Filename | Size | Date | Time | Version | Details |
|---|---|---|---|---|---|
| ZIP32VB6.DLL | 151,552 | 01/07/06 | 3:25 | v2.32 | = v1.1. For Archive feature. |
| WinGraphviz.DLL | 659,456 | 04/12/03 | 10:05 | v1.0.2.17 | For Enterprise Diagrams. Newer versions incompatible. |
| strtch.dll | 53,248 | 13/10/08 | 11:24 | v1.0.0.2 | For Enterprise Diagrams on Win98/ME. |
| ProASM.dll | 63,792 | 26/11/16 | v1.0.0.0 | For .NET assembly analysis. | |
| ProASM.reg | 2,414 | 23/11/10 | v1.0.0.0 | For .NET assembly analysis. | |
| EntDiag1.vst | For Enterprise Diagrams Visio export. | ||||
| constant.txt | For code review rule Verify accuracy. |
CheckLib is a little utility verifies that the required run-time files have been correctly installed on your computer. You can find it in your Project Analyzer directory. Double-click checklib.exe to run it. CheckLib locates the required files on your computer and checks to see whether the available version is the same as or higher than the required version. If any problems are found, it will suggest what to do next.
The following files are digitally signed by Aivosto Oy: checklib.exe, config.exe, mtxview.exe, proasm.dll, project.exe, strtch.dll, vbaplug.exe. If one of these files has no valid signature or is signed by someone else, Aivosto Oy cannot guarantee its safety or correct operation. In this case, load a safe virus-free copy from www.aivosto.com.
In order to analyze binary .NET assemblies (optional feature), you need Microsoft .NET Framework 4. It is installed by default on all modern Windows versions. You also have it if you have Visual Studio 2010, 2012 or 2013 on the machine. If you don't have any of these installed, follow the instructions below.
*) Windows 7 and Vista: Alternatively install .NET Framework 4.5, which is compatible with 4.
You can use Project Analyzer just fine even if you don't have the .NET Framework installed. It is only required for reading .NET binary files.
Minimum hardware requirements are not an issue. Any modern PC of the 2010s or 2020s will run Project Analyzer just fine.
Small and medium-sized projects get analyzed in seconds. Large analyses take a bit more time. On a high-end processor from 2014, a large project with 300 source files (200,000 lines) takes about 40 seconds. Double the size and it takes 2.5 minutes. A monster project with 2000 source files and 1.2 million lines runs in 20 minutes.
If you are analyzing huge projects, a fast processor will help. The number of processor cores is irrelevant because Project Analyzer runs in a single thread.
1 GB of RAM should be enough. Analysis of 1.2 million lines consumes about 0.6 GB of RAM.
High-DPI monitors are supported but not required.