Gary,
I think David Bertoni has experience with .NET 2010 and had success.
However,
the new project files have not been committed for VC10.
The sources for the companion Xerces-C v3.1.1 should be supported with VC10.
The quick way to prepare Xalan-C for VC10 is to copy the Project
directory for
VC9 into a new directory VC10, then let Microsoft .NET perform the platform
upgrade.
I would like to here of your success and problems!
Sincerely,
Steven J. Hathaway
- Xalan Documentation
On 9/21/2011 1:22 AM, Martin Elzen wrote:
Gary,
In my experience (with VS 2008) the compiled binaries for Xerces-3.1
work just fine with the SVN version of Xalan. I **don't know**,
however, how good the Xalan/Xerces experience is with VS 2010 ...
Martin
*From:*Kopet, Gary [mailto:gko...@websense.com]
*Sent:* Wednesday, September 21, 2011 7:04 AM
*To:* xalan-c-users@xml.apache.org
*Subject:* current Xalan C version -- 1.11
Hi,
I've been reading over the list archives and I wanted to be sure I've
got this right. I'm looking to get the latest Xalan C source, as on
the windows side we are compiling with MSVC 10
It looks like the svn trunk is the way to get it (as opposed to one of
the source tarballs). Also it appears that Xerces C 3.1.1 is the
compatible version. Is the source tarball ok for that, or should I get
that from svn also?
Thanks in advance,
Gary Kopet
Protected by Websense Hosted Email Security --- www.websense.com
------------------------------------------------------------------------
The information contained in this communication is intended solely for
the use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally
privileged information. If you are not the intended recipient you are
hereby notified that any disclosure, copying, distribution or taking
any action in reliance on the contents of this information is strictly
prohibited and may be unlawful. If you have received this
communication in error, please notify us immediately by forwarding
this email to mailad...@usoft.com and then delete it from your system.
USoft is neither liable for the proper and complete transmission of
the information contained in this communication nor for any delay in
its receipt.
