Don,

it depends on what your objective is: to use what you like because you like it? To use the best tool for the job? If the latter, you haven't tried VPM yet, so you really can't tell.

MEI's stuff is not bug-proof: I crashed the Anomaly Tracking System in 10-seconds on the log-in screen, because they hadn't accounted for 1 possibility. No one's stuff is bug-proof. Which is the real point of using a framework which is in active revision -- stuff gets fixed without your having to do it all yourself. Whether VPM, VMF, or VFE is best (I own them all, use ProMatrix, modify it to meet my needs) depends on your needs; but unless you have a multi-person shop capable of maintaining its own framework, using a commercially maintained framework is a necessity.

ProMatrix seems strange at first. I use it because a) it generally works; b) it generally has the features I need, or can be modified easily; and most of all c) when something is found to be broken, Steve fixes it, very quickly. I can't afford to hire someone with Steve's ability to work on the framework I use, but this way I get to use what he produces. The same would be true for Michael's work with VFE or Drew's work with VMF, of course.

Hank

>I work in an office of just two programmers. My co-worker insists that we use Visual Pro-Matrix for all new applications. I have some class libraries that I have gathered up on my own from several different sources (such as Micro Endeavors, Inc.) that I like to use for building apps.
>
>Does anyone have any articles or other materials that would argue against using Frameworks like Visual Pro-Matrix? Or any amunition that I can use to argue against using Visual Pro-Matrix?
>
>Thanks for your help,
>Don Knoup
>dknoup@landal.com
>LanDal Software Solutions, Inc.