User comments on Project Analyzer
These testimonials are spontaneous, authentic stories told us by real live Project Analyzer users.
Authentic feedback from real users
Analyzing large projects
Your Project Analyzer tool is top notch! We're using it to analyze projects well over 1 million lines of code. The depth and breadth the tooling is superb; the enterprise diagrams, Visustin, project metrics viewer, and dead code analysis have been quite useful for our current project.
Matt Warner, TaxWorks
Understanding existing code
The Procedure Tree List made me register the program. Just this one feature of Project Analyzer has saved me many hours (and my client many dollars) of frustration in trying to understand a client's VB program.
Converting from VB to C#
Project Analyzer has been very helpful. I've had to rewrite several applications for a client from VB to C#.Net. I'm not a VB developer, so this tool has been very useful in figuring out relationships and behavior.
Getting feedback when working alone
I just wanted to tell you again what a wonderful product you have. It struck me tonight, why I find it SO valuable. I don't work in an office with 20 other programmers, so when I program, I have no peers to give me feedback. Project Analyzer makes up quite a bit for that, giving me a 'project review and walkthrough' that would otherwise be impossible to get. Anyways. I'm going to get the problem count down to 0 before I go to sleep tonight, so I'd best get going!
Already in two 1-hour sessions I have learned more, and identified more required fixes, than I would have done in a month by reading and exercising the code unaided.
Identifying controls to replace
Ken Garrison, Fiserv
Reducing program size
The dollars spent have already paid themselves back. What your program did in less than 17 minutes would have taken me well over 200 hours. I used the time saved to add comments and do further optimizing of the code (original exe was about 1.2 meg, now it is only 700k).
It really solved a big problem we had. We have had a team of 3 people working on the same program for the past 3 years, it is very large. We were able to immediately shave 300k off the size of our executable!
Lance Keene, Sarbrook Company
I removed 7 files and 361KB of source code and the executable size was reduced from 908KB to 652KB. Needless to say, obtaining these results would have been impractical without a dead code detector.
Your product is superlative and using a simple seek and replace on the string functions (format -> format$ ...) I reduced my **compressed ** EXE by 14k. Aivosto, where have you been all of my life?
Cleaning up unused code
I purged about 20 dead source files and over 50 dead routines, and also found a number of bugs thanks to your option explicit checking. In our 150,000 line application, it only takes about a minute and a half to perform the initial analysis.
Spotting more dead code
Ken Halter, MS-MVP-VB in microsoft.public.vb.general.discussion
Improving quality of undocumented code
A couple of years ago we bought licenses for VB Watch Enterprise Edition and Project Analyser Enterprise Edition. I must say this has made the world of a difference to us, since very little of our existing code (60.000+ lines) was documented properly and we are with a small team of developers. Project Analyser made it possible to improve on quality and finally to make change decisions which affected many forms with confidence.
Theo de Roo, MAF Europe
Turning a project to another programmer
Danny Ringo, Odyssey Consulting Corp.
Discovering garbage in code
Torsten Borg, Fisa
Discovering your own faults
I am now using the code surf HTML facility to publish all our development code to our intranet web site allowing all developers to see their own programming faults identified in RED! This has resulted in a flurry of emails and fixes between the developers with inevitable improvements being made. I think they're all (including myself) a little embarrassed at having their coding inconsistencies there for all to see.
Chris Barber, Isotrak Ltd.
Running code review
Carl Hoelzlhammer, Emerson Process Management
The program is just absolutely great. I did 575 pages of documentation yesterday, and it was totally painless. I just can't say enough about what you have done here. Very, very good work.
I would normally take 1 month to document my software, now it takes me 1 day and I invoice for a month.
It definitely is worth acquiring this piece of software if Visual Basic is your tool for development. The various options available caters for just about every possible query one could have regarding the VB source.
Danie Odendaal, Microsoft
It is really a pleasure to work with a support like the one you are offering to us.
Armando Zuliani, Beta 80 Group
Great Utility - I have used it for many years and it keeps improving! A must have tool for any serious programmer.
Spontaneous, authentic comment at Developersdex.com
IMHO ist er jeden Cent wert. Ich nehme mal an, wenn Ihr eine Dead-Code Analyse laufen lasst, dürften sich eure Probleme gelöst haben. Es ist stellenweise erschreckend, wie viele Code-Leichen sich so in einem Projekt herumtreiben.
Translation: IMHO it's worth every cent. When you run a dead code analysis, your problems should be solved, I assume. At times it's scary how many code corpses wander in a project.
Thomas Ehlert in microsoft.public.de.vb
They have it already
Corporations, banks, airlines, universities, government units and thousands of individual developers in over 70 countries rely on Project Analyzer.
ABB, ABN Amro, Accenture, Alcatel, Alstom, Aon, AstraZeneca, Banco de España, Banco de México, Banco do Nordeste do Brasil, Bank of America, Bank of England, Barclays', Bayer, BBC, BHP Billiton, BMW Leasing, Boeing, Bosch, British Telecom, BUPA, Canadian Pacific Railway, Cap Gemini, Charles Schwab & Co, Cognizant, Compaq, Computer Associates, Compuware, ConocoPhillips, Council of Europe Venice Commission, Court of Justice of the EU, Credit Suisse, CSC, Daewoo Automotive Australia, Daimler, Digital, EDS, ExxonMobil, Federal Reserve Bank, Fujitsu, General Electric, Geoscience Australia, Glaxo Wellcome, Griffith University, Hewlett-Packard, Hilton, Honeywell, IAEA, IBM, Infosys, ITU, KPMG, KPN Telecom, Lockheed Martin, Lucent, Maersk Data, MCI Worldcom, Mercedes-Benz, Merrill Lynch, Microsoft, Mitsubishi, Motorola, National Australia Bank, Nine Mile Point Nuclear Station, Nokia, Norske Skog, Northrop Grumman, NSW Dept of Primary Industries, Oregon Secretary of State, Oregon State University, P&G, Philips, Prudential, Rockwell Collins, Royal Bank of Scotland, SAIC, SAP, Shell, Siemens, SNCF, Sony, Southwest Airlines, Tata, Teamware, Terex, TNT Post, Toyota Motor, Tyco, Unisys, University of Newcastle, University of Queensland, University of Surrey, University of Texas, University of Washington, UPS, U.S. Department of Labor, U.S. Department of State, U.S. Department of the Treasury, U.S. Postal Service, Wang Healthcare Information Systems, Wells Fargo, WHO, Wipro, Xerox, ...
Checking out Aivosto VB Project Analyzer's compatibility checklist
Visual Basic 6 to .Net Migration
Peter Aitken at DevSource.com
Pointing out where you need improvements
For all the modules containing code, you can view the module in a 'hypertext' view. This is similar to what you see in the VB code window, only more colourful and you can click on procedures to find out about them. You can also find out information about the module. This is one of Project Analyser's strengths. It gives you information like name, version, lines of code, and information about the number of procedures.
John Percival at Developer.com
WOW! This program is a MUST for every serious VB programmer. It has tons of cross-reference reports, code optimization suggestions and discover dead code. Rating: 5/5.
Aldo Vargas at Betanews.com
Thank you for sending us your comments.