2

Getting some odd build behavior as I remove all references to MSXML4 in my project, and replace them with MSXML6.

When I install MSXML using NuGet, or if I add it manually by referencing the dll in SysWow64, the reference immediately builds down to Interop.MSXML**2**.dll in my solution folder > obj > release.

The properties of the reference indicate it's version 6, but I don't have confidence as to which version is actually being used -- in large part because of the naming convention.

Do all versions MSXML compile into this interop.msxml2 file? It appears as though the namespace is MSXML2, but the naming convention is odd here.

Richard Chambers
  • 16,643
  • 4
  • 81
  • 106
Switch386
  • 454
  • 6
  • 19
  • 3
    `MSXML2` is the logical name of the library that resides in `msxml6.dll`. You can verify that it's version 6 by the fact that `DOMDocument60` is available. I don't see why you would need to use `MSXML2` from .NET though. – GSerg Aug 10 '17 at 22:32
  • Thanks for your response. Very old platform, but it's legacy--I'm just tasked with changing versions. – Switch386 Aug 11 '17 at 00:07
  • 1
    See also this question that discusses MSXML4 and MSXML6 and upgrading to MSXML6 https://stackoverflow.com/questions/1075891/what-became-of-msxml-4-0 as an answer or two has some additional information about various MSXML versions. – Richard Chambers Aug 14 '17 at 19:47
  • What nuget package delivers MSXML? I can't find any... thanks – StayOnTarget Nov 12 '19 at 17:19
  • It’s going back a couple years...I’m fairly certain I manually downloaded it, installed it into that legacy application, and checked it into git...because that’s what they were already doing. – Switch386 Nov 12 '19 at 23:17

0 Answers0