Been working on a bit of software that took advantage of the XML SDK offered by MS. Well, I had to stop for a little bit because I had to rebuild and reformat my HDD as well as work on other, more important projects.

So I come back to my old software and find that I forgot to reinstall the XML packages. So I hop over to MS and find they've moved on to XML 4.0 SP1 (I had XML 3.0 and vanilla 4.0). Install the newest package and find that most of my code is failing due to lines like thus:

Warning, it's Visual Basic.
Code:
Private Property Set IVBSAXContentHandler_documentLocator(ByVal RHS As MSXML2.IVBSAXLocator)
It seems that the MSXML2 object no longer behaves as it's expected to. Previous documents specify that one needed to reference MSXML2 to access the other objects inside. Now, it seems to balk at that reference.

Was this a noted change in the 4.0 SP1 package or something that was resident from my previous dual installation of 3.0 and 4.0? I had a class that started on 3.0 and we couldn't change to 4.0 since it would've broken a lot of code we worked on in the class. Yeah, it sucked. I ended up getting an A.

Anybody have any idea what I'm talking about?

I don't mind fixing the broken code, that's a part of life. I just want to understand the why.