I take a different approach to testing apps on a new(ish) OS, that , when
done, leaves a total blueprint of that OS's internal calls with any app
that I'm testing.
I switched over to this technique late in 1999, and never looked back.
I can understand the gripe and moan philosophy, but if I engage in it for
more than 3 minutes, I'm doing my product line a great disservice - and
come on - isn't that wot it's all about ?
You want yer software to work on new(ish) OS's, so you have New Users
Paying New Licensing Fees...
Or did I miss your point, in it's entirety?
Mondo Regards [Bil]
--
William Sanders / efGroup {rmv the DOT BOB to reply}
Mondo Cool TeleCom -> http://www.efgroup.net/efgcog.html
Failing dotNet Project? -> http://www.dotnetconversions.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
