Kylix wrote: > Is there a web site listing the different rules to follow when we program > a Win32 application.
http://msdn2.microsoft.com/ > For example, here at my company we were doing some test with our products > to see if they were compatible with VISTA, but we found out that > VISTA does not allow writting files anywhere but in Document > Settings\Account name\Application Data if you're not a Supervisor... That's not true. The person who has that account should have no restrictions on writing to that directory. Use the functions in my article to find out where the account's folder really is, though; you won't know in advance what the name of the profile is. http://www.cs.wisc.edu/~rkennedy/my-documents > It's only an exemple, but I'm sure there are others things like that, is > there a list or a develepement guide revealing all the architecture rules > to follow to ensure that our software will be compatible with future > Windows releases? Well, start by reading the documentation of any API function you use. If you copy and paste code you found somewhere else, make sure you actually undersand how the code you're using works. Follow the links in the documentation to read about the high-level concepts that the API functions are part of. In most cases, if it turns out that you need to change something in your program to make it work with Windows Vista, you weren't really doing it right for prior OS versions, either. Instead, you were taking advantage of things that were documented to be the wrong way to do things, but they happened to work anyway (such as writing to areas of the file system that don't belong to you). -- Rob
