Not required: Project Analyzer does not require Visual Basic, Visual Studio or the .NET framework installed.
Project Analyzer v9 is designed to work on regular Visual Basic projects regardless of code size or coding style. It analyzes the following types of systems:
The following project types are not officially supported. However, Project Analyzer seems to work with them. We don't guarantee the accuracy of the results, so use with care.
Project Analyzer does not work on any VBScript or ASP code, C#, QuickBASIC or any other language. ASP.NET: see above.
See also: Limitations and known bugs
The following files are required for Project Analyzer to run. If you have Visual Basic 6.0 installed, these files are already installed on your computer. If you don't have the run-times, download and install the run-time library package. You may already have downloaded it with Project Analyzer. Run the library setup program to install the required run-times correctly.
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 Required for COM analysis only.
Enterprise Diagrams additionally requires the following files in your Project Analyzer directory. They are included with the program download.
WinGraphviz.DLL 659,456 04/12/03 10:05 v1.0.2.17 strtch.dll 53,248 13/10/08 11:24 v1.0.0.2 Required in Win95/98/ME/NT only. EntDiag1.vst Required for Visio export only.
VBA Plug additionally requires a compatible Microsoft Office version installed on the same computer.
If you have trouble with some run-time library, put it in your Windows\System32 directory and register it with regsvr32.exe. Run as Administrator if necessary.
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, 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.
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.
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:
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.
©Aivosto Oy - Project Analyzer Help Contents