RE: Xerces COM/.NET

[Eric J. Peters]

Title: Message

I’ve been wondering why I’m doing this myself.  ;)   Mostly, I’m looking at comparing performance and memory use against the built-in XML functionality.  Although I’m concerned about the overhead of using COM interop, I’m very curious about what the overall results might be.   The rest is because I’m looking at (slowing) moving an existing codebase to .NET.  If I can use Xerces COM in the intermediate time, I have much more flexibility in working with XML in a mixed C++/C# .NET environment.  For example, if Xerces COM isn’t providing quite enough for a specific scenario, I can add custom functionality to aid in the migration; hopefully removing it later when further migration is complete.  And lastly, by design, the Xerces COM mirrors MSXML to some degree.  Therefore, if after the conversion is complete I find it does not perform as well as MSXML, switching would be less painful.   I guess the bottom line is that I’m making a ton of relatively uneducated guesses and assumptions.  I’d like to test Xerces COM in the .NET environment and see what shakes out.               -Eric.   From: Jesse Pelton [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 9:30 AM To: '[EMAIL PROTECTED]' Subject: RE: Xerces COM/.NET   I'm afraid I can't address your question, but I'm curious as to why you want to use Xerces with C#. I'm under the impression that the .NET Framework has rich XML functionality. Is it not so? -----Original Message----- From: Eric J. Peters [mailto:[EMAIL PROTECTED] Sent: Monday, November 24, 2003 9:19 AM To: [EMAIL PROTECTED] Subject: Xerces COM/.NET   Hi-               I have 2 quick questions:               I am trying to build the Xerces COM sub-project under VS6/WinXP.  I have installed the new platform SDKs, and I am not finding a way around the following error: "...\xerces-c-src_2_3_0\src\xercesc\com\StdAfx.cpp(28) : fatal error C1189: #error :  "xerces-dom requires an MSXML.H compatible with IE5 or later.  See http://xml.apache.org/xerces-c/build.html#BuildCOM for directions..."  I have followed the referenced instructions as best as I have figured since the paths are different under the new platform SDKs.  Has anyone solved this problem, or have any suggestions on where I start to try to solve this myself?               The reason I'm trying to build the COM is so that I can easily use Xerces from C#.  My second question is much less defined: I'm wondering if anyone has any experiences using Xerces in the .NET framework and would be willing to share their experiences.               Thanks!             -Eric.