Project Analyzer system requirements

Main requirements

Operating system: Windows 98, ME, 2000, XP, 2003, Vista or Windows 7.
Hardware requirements: 20 MB disk space, 128 MB RAM. We recommend 1 GB RAM and a fast processor (Intel Q6600 2.4 GHz or better) for analyzing large systems (over 500,000 lines). More
Run-time libraries: Either Visual Basic 6.0 or the Project Analyzer VB6 run-time library package ProA_VB60DLLs.zip. The package is included with Project Analyzer full download, or you can download it separately.
Framework, optional: Microsoft .NET Framework 4 (Client Profile or Full Profile). Only required for analysis of binary .NET assemblies in the Enterprise Edition. Note: Framework requires WinXP, 2003 or later. Download

Not required: Project Analyzer does not require Visual Basic, Visual Studio or the .NET framework installed.

Install and uninstall

Miscellaneous requirements

Microsoft Internet Explorer 4.0 or later to view help, 6.0 or later to view .mht reports.
Adobe Acrobat Reader 6.0 or later to read documentation, 4.0 or later to view .pdf reports.
Microsoft Office for analyzing VBA. See VBA Plug requirements.

Supported languages and projects

Visual Basic 3.0, 4.0, 5.0 and 6.0
Visual Basic .NET 2002, 2003, 2005, 2008 and 2010
ASP.NET solutions: The .vb files (codebehind classes) are analyzed. Web content files .aspx, .ascx etc. are not analyzed.
Office VBA, requires VBA Plug

Limited support projects

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.

eVB projects (.ebp) can be analyzed. Project Analyzer was not designed for eVB, but it seems to work with it.
Old VB.NET Compact Framework projects (.vbdproj) are supported to the extent they resemble normal VB.NET .vbproj projects. No special Compact Framework analysis features.
VSTO projects are not supported, but they may open. Analysis is inaccurate or incomplete.
Non-standard project files made with 3rd-party tools (other than Visual Studio or Visual Basic) are not supported. Project may be opened by selecting File|Analyze directory.
Unsupported. Project Analyzer does not work with VBScript, ASP, C#, QuickBASIC or any other language. ASP.NET: see above.

Required files

The following files are required by Project Analyzer. Newer versions are generally compatible.

Required system files

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. 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      
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.

Required other files

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.

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                                  v1.0.0.0     For .NET assembly analysis.
proasm.reg                                  v1.0.0.0     For .NET assembly analysis.
EntDiag1.vst                                             For Enterprise Diagrams Visio export.
constant.txt                                             For code review rule Verify accuracy.

CheckLib

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.

Digital signature

The following files are digitally signed by Aivosto Oy: checklib.exe, config.exe, mtxview.exe, 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.

Windows Vista

User Account Control in Windows Vista may prevent Enterprise Diagrams and file associations from functioning correctly. To configure these features, run Config.exe in your Project Analyzer directory.

Windows 95 and NT now unsupported

Project Analyzer has traditionally supported all Windows versions, starting from the old Windows 95 and NT. Support for these versions is no longer maintained starting with Project Analyzer v9.0. If maximal support is desired, please use a previous version.

Known issues:

Windows 95: The mouse wheel is not supported. Support is limited for DLL file analysis unless Imagehlp.dll is installed. The file has been available as a free download from Microsoft. Later Windows versions support these features out of the box.
Windows NT: Absolute minimum version is NT4 with SP3 or later. Other limitations are unknown.

Performance and hardware recommendations

Code analysis is processor intensive. The following speeds were tested on Intel Core2 Quad Q6600 2.4 GHz with 2 GB RAM.

Typical projects (10,000 to 150,000 lines) take 2 to 15 seconds to analyze. Very large systems, ones with 0.9 to 1.6 million lines, take approximately 5 minutes. Performance varies from 4000 to 13000 lines per second, depending on complexity. Large analyses run slower than small analyses.

For very large systems, we recommend a processor comparable to or better that Intel Q6600. Project Analyzer runs in a single thread, so a multi-core processor does not really make a difference. Yet we recommend a processor with 2 or more cores to run Project Analyzer in the background.

1 GB RAM is enough for most uses. Analysis of 0.9 million lines requires approximately 300 MB RAM.

Credits and additional terms

WinGraphviz: WinGraphviz.dll v1.0.2.17 by ood Tsen; based on Graphviz by AT&T
Info-ZIP: zip32.dll v2.32, renamed as zip32vb6.dll; Info-ZIP license terms