It has been more than a month since the Xerces release and now we are thinking about releasing XalanC 1.8.0, compatible with Xerces 2.5.0
Between the new changes in the release are:
- Compatibility with Xerces 2.5.0 and (optional) ICU 2.6.1 - VC7(2002) support
[rest snipped]
Please skip VC7 (2002) and go straight to VC7.1 (2003). There are no problems with the code, we are using it as-is on VC7.1 for more than a year. Of course, we had to play a bit with project files/makefiles, but no big deal...
I would agree if you're going to go to vc7, go straight to 7.1 (2003).
However, if you distribute vc7 project files, it means the project files cannot be loaded by anyone running vc6. As far as I can see, most people have *not* upgraded to vc7. I'm not sure what to do about this, but I suspect you'll get a lot of complaints. It will certainly cause me problems -- I can't upgrade until my coworkers do, and that's not my decision. So I'll be forced to create vc6 projects.
You could supply two sets of project files, but that's a support headache. Does anyone have any experience with this, perhaps automated ways to convert project files back and forth?
--- time for a quick web search ---
Hmm, I see a vc7 to vc6 project converter at codeproject. Maybe that would do. Has anybody used it?
Don
