You searched for the word(s): userid:663675

More Search Options

RSS Available

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  Eric, You didn't miss the topic, but, sorry, I don't see logic in your answer. Of course client machine can have old version of MSXML. But in all the cases Microsoft.XmlHttp is enough to test. For older systems - it is the only variant, for systems supporting MSXML2 - both MSXML2.XmlHttp and Microsoft.XmlHttp instantiate the same instance of XMLHttp object and the maximum version is MSXML2.XmlHttp.3.0. So the question WAS AND IS "why to test BOTH?". Well, you almost convinced me

  Posted to Client Side Web Development (Forum) by AGS777 on 8/17/2007

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  Wukfit, First of all, thanks for the detailed answer. I am sorry for not making my self clear in the last post. It was some time ago since I asked the question and I clarified almost all the related question to myself since then. I read all I could find, including, of course, the post from Microsoft about using right version of MSXML that I read back then in October 2006 and posted here when recalled about this thread. But it is just to explain why there is nothing new for me in your previous answer

  Posted to Client Side Web Development (Forum) by AGS777 on 8/16/2007

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  WukFit, Thanks, but still nothing new. The link you have mentioned is already present in the second post of the thread. And I still continue to believe that MS folks writing Microsoft AJAX Framework had some reason to verify both ProgIDs. var progIDs = [ 'Msxml2.XMLHTTP', 'Microsoft.XMLHTTP' ]; But probably this secret is doomed to stay unrevealed. Alexei

  Posted to Client Side Web Development (Forum) by AGS777 on 8/13/2007

• Re: ASP.NET 3.5 CLR

  Thanks, Mikhail.

  Posted to Visual Studio 2008 (Forum) by AGS777 on 7/26/2007

• Re: Applying master page at a folder level

  Thanks for the explanation. Alexei

  Posted to Visual Studio 2008 (Forum) by AGS777 on 6/25/2007

• Applying master page at a folder level

  Hi, It seems there is a problem in design view of VS "Orcas" Beta1 when I am trying to edit content page with a master page applied at a folder level. For example web.config file contains following sections: < location path= "Subfolder" > < system.web > < pages masterPageFile= "~/MasterPages/Subfolder.master" /> </ system.web > </ location > < pages masterPageFile= "~/MasterPages/Main.master" > .... When I open content page

  Posted to Visual Studio 2008 (Forum) by AGS777 on 6/24/2007

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  Eric, Yes, I read the article several months ago, but it doesn't clarify the questions. Thanks Alexei

  Posted to Client Side Web Development (Forum) by AGS777 on 3/15/2007

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  Eric, I am terribly sorry Eric that it took three posts to understand my question :). I really thought that it was well-defined even in the subject of the thread. Yes I'm aware of side by side and replace installation modes. So the "something like that" doesn't help me. Microsoft.XMLHTTP and MSXML2.XmlHttp ARE BOTH VERSION-INDEPENDENT. As far as I understand you think that MSXML version marked with Microsoft.XmlHttp ProgID can differ from one marked with MSXML2.XmlHttp. It doesn't correspond to my

  Posted to Client Side Web Development (Forum) by AGS777 on 3/15/2007

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  Thanks again Eric, but sorry for my stupidity I don't see an answer in your question. I am asking exclusively about XmlHttp request object, not about DOM Document with all the differences regarding XSLT engine or Schema validation. And, once again, I am talking about VERSION-INDEPENDENT ProgIDs: namely MSXML2.XmlHttp and Microsoft.XmlHttp . As far as I understand for the given browser on the given machine both of them will instantiate exactly the same instance of XmlHttp object of exactly the same

  Posted to Client Side Web Development (Forum) by AGS777 on 3/15/2007

• Re: Difference between MSXML2.XmlHttp and Microsoft.XmlHttp ProgIDs

  Thanks, Eric But the question actually was about version-independent ProgIDs. I think I understand well enough the differences between various versions of the library (thanks to article I mentioned in the previous post). And I know that MSXML2 namespace is newer than Microsoft. What puzzled me is why all major client-side frameworks test both version-independent ProgIDs to instantiate XmlHttp object: MSXML2.XmlHttp and Microsoft.XmlHttp while both of them stick to MSXML3 at best. I mean if you don

  Posted to Client Side Web Development (Forum) by AGS777 on 3/15/2007