Each configuration is dependent upon different coders to keep it maintained. Since I have Visual C++ 6, I maintain the Visual C++ 6 project files. I don't (and can't) maintain the Visual C++ 2005 project files, and I can't speak for those who do.
Whoever added Visual C++ 2005 to CVS isn't maintaining it, which is rather inconvenient for the people who download it from CVS. I'm starting to wonder if I should remove it from CVS, considering how many people are being misled.
Even though I haven't actively participated in active development for a long time and only started reading the forums at all again recently, I know that there have been efforts to get the 2005 project files working since they were committed. IIRC phreak fixed them. Kazan addressed a thread to you a week ago because he discovered that one of your changes broke compatibility with MSVC2005, and you actually responded to that thread, so you should know that working project files exist. Backslash also uses MSVC2005, AFAIK.
However, AFAIK, Kazan doesn't have write access and nobody committed the fixes he posted in July. That is, at least in part, your decision. Obviously nobody can maintain the MSVC2005 project files if the people who want to maintain them are restricted from applying the changes, and nobody who can apply the changes does it for them.
OTOH, given that it's been about a month since Kazan posted those fixes, you'd probably want to ask him to see if he'd be willing to post an up-to-date set.
