Спешу страшно. Может поможет.
Раскопал в своих развалах. Бегло просмотрел. Не знаю.
-----------------------------------------------------------
Right before the code sample he says the code utilizes MSXML 3.0 but the code actually creates MSXML 2.0 Objects
Set srvXmlHttp = CreateObject("MSXML2.ServerXMLHTTP")
Set xmlResult = CreateObject("MSXML2.DomDocument")
- Anonymous 09 Feb 2001Respond
Re: Slight discrepancy
MSXML2 it's just a namespace... MSXML3.DLL (Microsoft XML version 3) uses MSXML2 in the namespace. In VB this is the Project Name. In IDL this is library. Open the DLL in OLEVIEW or Object Browser(VB) to see the namespace IDL Sample: [ uuid(F5078F18-C551-11D3-89B9-0000F81FE221), version(3.0), helpstring("Microsoft XML, v3.0") ] library MSXML2 { ...
-
fgaluppo@hotmail.com 13 Feb 2001Respond
Re: Slight discrepancy
That is MSXML3.0. The ProgID isn't the same as it's designed to be used side-by-side hence MSXML2 rather than MSXML
- Anonymous 13 Feb 2001Respond
Re: Slight discrepancy
MSXML 3.0 objects are called MSXML2.Whatever.
- Anonymous 13 Feb 2001Respond
Re: Slight discrepancy
Yeah ,well Actually i think that's the way you reference it .because,the other day i downloaded the version 3 xml sdk,and it installed version msxml2.dll,anyway search for the tlb's or dll's and check the properties of the file you'll see.
- Anonymous 13 Feb 2001Respond
Re: Slight discrepancy
Yeah ,well Actually i think that's the way you reference it .because,the other day i downloaded the version 3 xml sdk,and it installed version msxml2.dll,anyway search for the tlb's or dll's and check the properties of the file you'll see.
- Anonymous 13 Feb 2001Respond
Re: Slight discrepancy
I meant msxml3.dll(2 is the namespace,I 'm anti MS but they re confusing sometimes,gotta get used to that..
- Anonymous 13 Feb 2001Respond
Re: Slight discrepancy
the msxml3.0.dll returns "MSXML2 as it's dll name. he's right.
- Anonymous 14 Feb 2001Respond
Re: Slight discrepancy
If you've used the Msxml parser data model, you would know that Msxml 3.0 is accessed by the "2" ending. To clarify: "Dim oDomDoc as MSXML2.DomDocument" is code that accesses MSXML3.dll whereas "Dim oDomDoc as MSXML.DomDocument" accesses MSXML2.dll I can't explain the logic here, but I like to write it off as a "Feature"
- Anonymous 20 Feb 2001Respond
The Right Time to Migrate
There a several data access evangelists, but it's rare to find one that tells scripters the truth, like Dino. I'd say this is well said - and said at the right time.
- Anonymous 09 Feb 2001Respond
Dino Rocks!
Please keep writing these great articles.
- Anonymous 08 Feb 2001Respond
in like a lion, out like a lamb (dino)
the article started out defining how and when to migrate, and then trailed off somewhere .... Will there be a part II?
- Anonymous 08 Feb 2001Respond
Some lesser know issues...
There are a few really important things that you should keep in mind, that weren't mentioned in this article. 1. You can access .NET classes through web services, but expect a huge performance penalty compared to COM/DCOM. This also assumes that it's a trivial thing to retrofit your code to deal with XML instead of recordsets. 2. Right now, the only ADO.NET is Beta 1. Expect the name of objects and methods to change in Beta 2, meaning if you write a lot of .NET code today, you will have some work to do when Beta 2 releases. On the plus side, there aren't supposed to be any incompatible changes between Beta 2 and RTM. 3. Right now, .NET doesn't support connection pooling on the SQLConnection object (which is what you'll want to use if you're talking to SQL server). As a result, you'll see another performance hit until Beta 2 releases. 4. There are some things that just don't exist in ADO.NET. For example, you can't create server side dyanmic, keyset, or static cursors (not that these were usually good ideas), so if you have code that depends on these, expect some work. 5. It would have been nice to actually seem some ADO vs. ADO.NET code. Unfortunately, there wasn't any at all. Basically, this article really sucks. And it's not just the heaven/hell/change of season junk that fills up a bunch of space without even providing a good analogy. It's more that the author wrote an article without really knowing what he's talking about. Dino, how many times have you actually implemented this scenario in the real world? Never. Don't get me wrong, ADO.NET rocks. You will want to move to it. But wait at least until Beta 2 releases.
- Anonymous 08 Feb 2001Respond
Great Article...
Dino is really a great Writer and Speaker(VS Live - SFO 2K1)...
-
fgaluppo@hotmail.com 08 Feb 2001Respond
Re: Great Article...
he is a son of darkness
- Anonymous 12 Feb 2001Respond
