Due to problems associated with installing MSXML4 (like this) we want to switch to MSXML6. Are there any known issues associated with this or is such transition smooth and painless?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Due to problems associated with installing MSXML4 (like this) we want to switch to MSXML6. Are there any known issues associated with this or is such transition smooth and painless?
This comment isn’t so much about the 4 to 6 transition as it is about the MSXML6 installer itself. Apparently some people do experience problems getting it installed properly. When not properly installed, it breaks the Add-In Manager in Visual Studio.
Quote from this page:
“There is a reported problem that happens when MSXML 6.0 is not installed correctly. In this case the Add-In Manager doesn’t show any XML-based add-in (using an .AddIn file for registration). It shows only registry-based add-ins. So, if the Add-In Manager is empty when it should show several installed add-ins (not only yours), try reinstalling MSXML 6.0.”