Ellonnic2 wrote:
Hi Dave,
Thanks for your reply.
I only built the sample code, not the Xalan or Xerces source code itself.
To be more specific, I downloaded and used the binary distribution of both
Xerces (xerces-c_2_7_0-windows_2000-msvc_60.zip) and Xalan
(Xalan-C_1_10_0-win32-msvc_60.zip).
Trying to step over this very line:
theResult = theXalanTransformer.transform(argv[1], argv[2], cout);
consistently causes the "Unhandled exception at ... in XalanTransform.exe:
...: Access violation reading location ...." failure.
Is it because I'm using Visual Studio 2005 to build this and the binaries
were built using Visual C++ 6.0? If so, how do resolve that without having
to upgrade Visual Studio versions?o
You can't mix the binaries built with VS6 with binaries you built with
VS2005 -- Microsoft's run-time libraries are not compatible.
If you need to build with VS2005, first download the Xerces-C vs2005
binaries, or build Xerces-C 3.0.1 from the source code:
http://apache.securedservers.com/xerces/c/3/binaries/xerces-c-3.0.1-x86-windows-vc-8.0.zip
http://apache.securedservers.com/xerces/c/3/sources/xerces-c-3.0.1.zip
Then, you'll need to check out the latest Xalan-C source code from the
Subversion repository. It's fairly easy to do using a GUI program like
TortoiseSVN:
http://tortoisesvn.net/downloads
After you install TortoiseSVN, open Windows Explorer and navigate to the
folder where you want to check out the sources. Right-click in the
folder, then enter the following URL in the edit field:
http://svn.apache.org/repos/asf/xalan/c/trunk
You can also specify a subdirectory or the checkout in the second edit
field, if you want.
Then, you can follow the Windows build instructions here:
http://xml.apache.org/xalan-c/build_instruct.html#dotNet
Note you'll need to open the project files for VC8 instead of VC7.1,
since you're using VS2005. Also, please make sure you put the Xerces-C
DLLs (both debug and release) somewhere on your path, so they will be
found during the Xalan-C build process. I typically add the Xerces-C
output directories to the path, but you may find it easier to put them
in a single directory and put that directory on your path.
If you have any questions or problems, just post a reply.
Dave
