The primary gotcha is that .Net will link in a new msvcr70.dll, which has a different name from the existing one. So Xerces will use the one it's been built for (the current one), but the client apps built with .Net will link in the new one. So you'll be in the 'one too many runtimes in the kitchen' problem, same as with mixing debug/production runtimes.
Perhaps they are smart about this and get around it somehow, but I'm figuring not. ------------------------------------- Dean Roddey The Charmed Quark Controller [EMAIL PROTECTED] www.charmedquark.com -----Original Message----- From: Gert van Spijker [mailto:[EMAIL PROTECTED]] Sent: Friday, June 14, 2002 2:10 PM To: [EMAIL PROTECTED] Subject: Re: Will Xerces-C Support Visual Studio .NET ??? > > If so, when? This upcoming release? > > > > -Bob > I had no problem compiling 1.6.0 with .net... > > In the projects\win32 directory, > - xcopy /s VC6\*.* VC7\ > - handedit the .dsp to change 'VC6' to 'VC7' > - open the .dsw in .net. > - compile As far as building goes, you can just open the existing MSVC 6.0 workspace; VS .NET will offer to convert to 7.0. But somehow I think this is not what Bob means. What does he mean with "Will Xerces-C Support Visual Studio .NET ???" He surely knows VS .NET can build existing Xerces releases. As far as I know the .NET C++ compiler doesn't introduce any new features that need to be supported. Probably Bob can clarify his query? Gert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
