Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Installing MSXML v3.0
Message
 
To
02/04/2002 11:05:06
James Blackburn
Qualty Design Systems, Inc.
Kuna, Idaho, United States
General information
Forum:
Visual FoxPro
Category:
InstallShield
Miscellaneous
Thread ID:
00639086
Message ID:
00640141
Views:
22
Be very careful with MSXML 4.0 because it changes the way many things work in MSXML especially XPATH queries in SelectSingleNode() and the like. THe most serious issue is that Default namespaces are no longer supported and must be explicitly assigned, which requires some extra code.

+++ Rick ---

>Final resolution, I had to add msxml3.dll, msxml3a.dll, msxml3r.dll to the windows system dir. I marked only the msxml3.dll to self register. All work well now.
>
>>I thought someone else might benifit from what I found out. I found the following bug on the Install Shield web site. I called MS and they are having me try MSXML vs 4.0 I will see if the works with VFP and then see if it will install properly.
>>
>>
>>
>>BUG: MSXML 3.0 Merge Module Not Installed at Run Time
>>Document ID: Q105789
>>This article applies to the following:
>>Product(s): InstallShield Developer 7.x, InstallShield Express 3.5x
>>Last Revised On: 01/02/2002
>>Symptoms
>>If you include MSXML 3.0 Merge Module in your setup, it does not get installed.
>>
>>
>>--------------------------------------------------------------------------------
>>
>>Cause
>>There is a bug in the MSXML 3.0 Merge Module, which causes it to bahave this way. This usually happens if you associate the MSXML 3.0 Merge Module to a feature that is not installing any files on the system.
>>
>>
>>--------------------------------------------------------------------------------
>>
>>Resolution
>>Microsoft recommends that customers experiencing this issue should contact Microsoft Technical support. To fix the merge module, you will have to open it in ORCA, Developer 7, or any utility that allows one to modify or create Merge Modules. Thus, it is recommended that customers experiencing this issue should contact Microsoft Technical Support for further assistance.
>>
>>
>>--------------------------------------------------------------------------------
>>
>>Workaround
>>Make sure that you associate the MSXML 3.0 Merge Module to a feature that installs files on the system to work around the bug in the Merge Module.
>>
>>
>>>>I need to have msxml installed with my application. I checked the msxml merge module and rebuilt the app and it still is not installing the correct version. Is there somthing that I am missing? Also, how can I tell what version is installed?
>>>
>>>James,
>>>
>>>Take a look at the following MSDN link:
>>>
>>>http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q278674&LN=EN-US&SD=msdn&FR=0&
>>>
>>>The article is titled: "Determine the Version of MSXML Parser Installed on a Computer" In this article they describe some of the different ways the XML parser can be installed on your computer (or the user's computer) that are not as obvious as they should.
+++ Rick ---

West Wind Technologies
Maui, Hawaii

west-wind.com/
West Wind Message Board
Rick's Web Log
Markdown Monster
---
Making waves on the Web

Where do you want to surf today?
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform