Thanks for the explanation. I hoped that it is simpler.
I understand importance of testing. I must admit that such approach seems to work because VFP7 is more stable than VFP6 . However from common sense point of view it still seems strange to test thousands lines of code again when there are only a few changed lines. I still hope that in a future there will be an easier solution and VFP8 will be available to greater audience than it is today.


>>I can not believe that VS.NET, SQL Server and other MS products need two separate full testing for commercial and evaluation version.
>
>Believe it. I just looked at VS's test plan for just the trial version and just for testing setup. NDA prevents me from getting into specifics, but suffice it to say they test more than I even thought of.
>
>> It would be wasting of time and money. Technology of making evalution >version should eliminate such need. I can not believe that MSFT can't do >that.
>
>If the binaries are changed, it gets retested, period. Once the binaries change, things move around in memory and who knows what broke. Setup builds need to be tested to insure the build process worked as expected. To not do so would be a sign of negligence on the part of the test team. No amount of current technology is going to change that, and I'm not convinced it could be overcome in the future.