Lorenzo Barbieri @ Weblogs.Asp.Net

Just think, if professionals are not sure what to do, what is the little old lady in Pasadena going to make of all this....?

It's nice that you think that Microsoft always releases products that follow the behavior of release candidates. After all have you heard of Chicago or whatever the release candidate for Win 2000 was called - did all features of the applications make it into the actual system? No. The other factor is that we don't always know what is hard coded in the release candidates. If I owned a business I would wait for the actual release. How do I know what my customers are going to be using?

After all it is MICROSOFT that controls the code, contents of the release and the development cycle. How do you know that you are ready? Only true TESTING is the verification tool that has to be conducted. Then after the testing is done - true software issues can be worked out.

Best of Luck to you and your customers.

I don't know that my sites will ever be ready for SP2. My clients are all using Pervasive SQL backends to custom applications that SP2 is known to break. I think we'll be waiting on SP2a that doesn't break Pervasive/btrieve calls...because I don't think the app vendors will get their stuff together in time

"After all have you heard of Chicago or whatever the release candidate for Win 2000 was called - did all features of the applications make it into the actual system? No."


Chicago = Windows 95

The RC releases of Windows 2000 were 99.9% unchanged from the retail product - As with virtually every Microsoft RC release. In fact, RC3 of Windows 2000 was available for several months before RTM, and was virtually identical to the final build.

Nick: What breaks with PSQL & XP-SP2? I've got customers that have installed, answered "Yes" to allow the database client to access the firewall, and have had no problems. I'd be interested to hear your story...