Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
A while ago, I posted an item regarding a possible cause and resolution for 1935 or 2908 errors during Visual Studio 2005 setup. Since then, I have heard from several customers who have run into similar issues during Document Explorer 2005 setup.
After thinking through these scenarios in more detail, I realized that it is more likely that Document Explorer 2005 setup will fail with a 1935 error than it is that Visual Studio 2005 setup will fail with a 1935 error because Document Explorer is installed as a prerequisite before setup ever tries to install Visual Studio. Therefore, if the .NET Framework is in a bad state (which is generally the cause of these 1935 errors), then the first place it will typically be seen is in Document Explorer setup because that setup package needs to be able to install assemblies to the GAC and requires a functional .NET Framework 2.0 installation on the system to be able to do so. If Document Explorer setup fails, Visual Studio setup will not even be attempted.
Even though this is a bit of duplication from my previous post, I want to list the steps that can be used to workaround this issue with Document Explorer setup in case folks run into this issue.
When Document Explorer 2005 setup tries to install assemblies to the GAC, it may fail because the .NET Framework 2.0 is not correctly installed on the system. In the cases I have seen where this has happened to customers, the underlying problem was that setup detected that the .NET Framework 2.0 was already installed and skipped that prerequisite step. However, the machine did not actually have the .NET Framework 2.0 installed, but instead only had the registry key that setup uses to detect whether or not the .NET Framework 2.0 is installed.
I found that the machines had the following orphaned registry key/value that setup uses to determine that .NET Framework 2.0 was already installed:
In the cases I have seen, the customers deleted this key/value and re-ran Visual Studio 2005 setup, and setup correctly detected that it needed to install the .NET Framework 2.0, and after installing that, Document Explorer 2005 and Visual Studio 2005 setup worked perfectly.
Note - if the above workaround does not help, I would suggest taking a look at the Document Explorer 2005 troubleshooting tips that I previously posted.
Where to get Visual Studio 2005 and the .NET Framework 2.0 Where to download the .NET Framework 2.0 redistributable
Woops, when I install VS2005,a error popup during install document explorer,it says" cannot find one or more components,please reinstall the application."
then click ok button , then installation continue, but when the Visual studio component was installed, and wizard execute action: HxMerge_VSCC_v80, the error dialogue popup again: title<Micosoft CLR Debugger>, cannot find one or more components,please reinstall the application.
click ok, then the same error dialogue popup:
title<Micosoft Visual studio Macros>,cannot find one or more components,please reinstall the application.
click ok, the same error dialogue popup:
title<Micosoft Visual studio>,cannot find one or more components,please reinstall the application.
click ok, the wizard can install the remain components successfully.
at last, when I start the Visual studio application, the error popup:title<Micosoft Visual studio>,cannot find one or more components,please reinstall the application.
then Visual studio close.
God, how can I solve it?
Hi Coodragon - What operating system are you using when you try to install Visual Studio 2005 and see these errors? Also, can you check in your application event log and see if you see any exceptions that are logged around the time that you see these errors during setup?
During installation i am getting struck when it reaches "HxMerge_VSCC_V80" every time i get this error.
When i uninstall visual studio i get strucked in between itself on that time power went off. After power came i tried to uninstall it again on that it shows an error message in dialog box "Already you have uninstalled" eventhough i am getting an error
Hi Charu - You can use steps like the ones listed at blogs.msdn.com/.../487096.aspx to manually remove any components that did not uninstall correctly when the power went off.
If you try that and the install still fails, then can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com), and then reply back here and provide a link that I can use to download your log files and take a closer look?
Thank God I stumbled upon this. This was the answer for why I couldn't install it VS2005 on Win 7. Thank you