From: Olivier M. <om...@ti...> - 2007-03-21 10:22:05
|
Le 21-mars-07 =E0 10:43, Paul Reeves a =E9crit : > I still get the feeling that MS have produced a crappy solution to a > problem that they created for themselves. And, as usual, it has a > complexity level designed to bamboozle about 99.9% of the population. Oh yes, crappy solutions. Go try to find one official, politically =20 correct directory where an installed program might want to create, =20 read and write files that will be shared by all users who will run =20 that application... There somehow is one which is CSIDL_COMMON_APPDATA, but the access =20 rights are such that a standard user (w2k, winxp, vista) won't be =20 able to write there. The only provided solution is to have the =20 installer update the rights of that location. Which all softwares I =20 have seen doing so, do wrongly, trashing some other special rights. =20 Adding more crap to the crappy crap. There might come a day when poor Windows subjects will have to pray =20 Bill The Great before clicking the Start button... ;-) Really so much time and money to get to *that* (vista)? And people still think they get access to a masterpiece of the 21st =20 century technology? Bah... > BTW, in case anyone missed it, here is an amusing article about the > quality of MS developer documentation: > > http://www.regdeveloper.co.uk/2007/03/08/msdn_gloom/ Along the same line, the documentation for the Win32 API DeleteFile =20 which you can read here (http://msdn2.microsoft.com/en-us/library/=20 aa363915.aspx) in its newest version still gives invaluable advices =20 to developers, advices I could not live without: "To prevent loss of data, close files before you attempt to delete =20 them." Yeah sure. Thanks Mom. --=20 Olivier Mascia |