I am getting the following error when trying to install Visual Studio 2005 on my 64bit, Vista computer:
"1305.Error reading from file
C:\Program Files (x86)\Microsoft
Visual Studio 8\Microsoft Visual
Studio 2005 Standard Edition -
ENU\SITSetup.dll"
I have successfully used the same DVD's to install Visual Studio on my old XP machine, and I can find the file (SITSetup.dll) on the DVD...and copy it off...so I don't think this is a case of having a bad DVD. At the time the error message pops up, I can see the file on my hard-drive, but it has a 0 size.
I've Googled this problem, and found some ideas, but nothing has worked thus far. Any suggestions would be appreciated.
I have to confess on this..especially since someone voted for the question.
Everything I said in my original posting about using the disks successfully in the past -was true. However, after innumerable shots at trying to get this install to work, I finally went back and looked at the DVD, and found that either myself, or one of my kids, left traces of food stuck to the underside of the DVD. After cleaning the DVD off, the install worked fine. This is embarrassing.
I assumed the DVD was fine because I had used it before, as well as being able to copy files off it. However, the last time I used it was years ago, and sometime in between then and now...something got on it. I guess the lesson here is never skip the basic checks!
I just installed it yesterday on my Vista box (32-bit, which may be the problem). It seemed to go through fine so I don't know what to tell you other than than when I first launched the app it notified me of "known compatibility issues" and recommended that I install both the SP1 and Vista SP! updates. No further issues past that.
As such, I would suspect either a problem with the 64 bit OS (though Microsoft says it's fine...) or other software on your machine. If you have a virus scanner running, for instance, disable it while installing.
If your Vista machine is a guest running under VMware, try copying the entire DVD to your hard drive and install from there.
I don't know if the same random glitches occur on real machines.
I can confirm that this is a problem for me on Windows 2008 Server while not on XP or Vista (all 32-bit). Not sure why there's any kind of issue here but it seems to be permissions related.
Also tried run as administrator etc but no luck.
Related
This might be a stupid question, but I can't solve it for hours and it is killing me.
I'm trying to install visual studio in my lab computer, which runs Win7. The problem is, when I execute visual studio installer, it does not do anything after showing the Visual studio logo and is utterly unresponsive (only a black square pops up). At first, i thought it might be loading for a long time, but after leaving for few hours and still it does nothing.
I've tried to install it using ISO images, or even tried previous versions(2013 and 2012) but failed.
Formatting would be a simple answer, but it is practically impossible since it is used by multiple members in our lab, so I can't occupy it for too long to format and installing all other existing software.
How can I solve this problem?
Thank you for even reading this question. I would appreciate even more if I can get an answer!
You should install all Windows Updates and also update the GPU driver. The setup is based on Windows Presentation Foundation (WPF) which uses GPU to accelerate the UI so also up to date drivers are recommend.
So many things happened that I don't know where to start. Seriously, shouldn't this be simpler?
Edit: Someone here knows how can I contact Microsoft to tell this? Or even, can someone tell them about this problem?
I have the last Windows 10 desktop and also have Windows Phone 10.0.10512.1000. I installed Visual Studio 2015 with tools for Universal Apps development (and also 8.1). I have a Lumia 730.
So I connected my phone with my USB cable. Everything fine, the phone gets recognized and I can navigate through the folders.
Then I started Visual Studio 2015 and created a blank universal app. Compiled and tried to deploy. Now this is happening to me: Visual Studio hangs for some moments. Eventually I get an error telling that the device was not found (DEP6200).
I already tried dozens of solutions:
disconnecting from wifi in my laptop and my phone
restarting the IpOverUsbSvc service
rebooting the computer and the phone
deleting the devices in the Device Manager
Registering and Unregistering the phone (it sometimes works)
All of the above with the phone screen unlocked
disabling Hyper-V
disabling firewall
Other solutions that failed miserably
I also tried to use that Windows Phone Developer Power Tools. When I try to use it, it asks me to install some "Phone Tools Update Pack", but when I try, it says that the operation didn't succeed, and also shows the NRE message string (object reference not set to an instance of an object).
I can go through the phone's folders without any problem. I tried to reinstall the drivers... i tried everything.
It's quite sad.
Do you guys can think of some more thing to check?
EDIT: I tested this app before doing all this: https://blogs.windows.com/buildingapps/2015/07/09/just-released-windows-10-application-deployment-tool/
And it worked. If that's the case, is Windows Phone 10 deployment over Visual Studio working already or we have to wait some more time?
Edit2: After making some changes to my app manifest and choosing "ARM" config, now I get this:
1>Deploying to SD Card...
1>Updating the layout...
1>Copying files: Total <1 mb to layout...
1>Checking whether required frameworks are installed...
1>Framework: Microsoft.NET.CoreRuntime.1.0/ARM, app package version 1.0.23117.0 is not currently installed.
1>Framework: Microsoft.VCLibs.140.00.Debug/ARM, app package version 14.0.23019.0 is not currently installed.
1>Installing missing frameworks...
But it just stays there. It's stuck, and it stays there forever. At least I got some info... Its more or less the same steps that WinAppDeployCmd does, but the command line app does it successfully.
Somehow the problem got solved. I created a brand new project and did this:
1 - In your phone, try disabling the developer mode on your phone. What an unexpected development!
2 - Disable the "phone discovery" thingy. I don't know the name of this configuration in english (as my phone is in Portuguese). Just in case.
3 - Choose the correct architecture. This is obvious, right? In my case, ARM. If you try deploying with x86 or x64, it should give you an error. For me, it didn't.
From now on, you should be able to deploy your apps in both developer mode and non-developer mode. It just works, somehow. And it might NOT work for you, sorry. I think I got lucky.
It worked even after a reboot. So the solution is "pretty solid" (in an universe where gelatine is pretty solid).
I had the same problem. I tried the fix of the comment and went to devices manager.
Under USB-Devices there were three Lumia 920s listed.
I selected the second one and clicked on uninstall.
At the end it asked me to restart the Computer. I clicked on NO.
(When I uninstalled the first or third one, it didn't ask me that).
Then the error disappeared (now another common one appears (HRESULT: 0x80073CF6))
I have a Lumia 950 xl, with windows 10 installed, anniversary version. I had the same problem, and my solution was to turn on 'Device discovery' and 'Device Portal', and also keep the 'Developer mode' on.
I believe the only necessary option was the 'Device discovery' though!
Just in case someone still runs into this issue, I had something very similar with my Visual Studio 2015 professional update 1 but I couldn't even deploy to an emulator.
The issue has gone after I upgraded to Visual Studio 2013 update 3.
I had the same issues on Windows 10 with Visual Studio 2015. I updated the the UWP SDK to Anniversary Edition Build 14393, set the target framework to this and it worked. I guess the incompatibility between the device version and sdk version was not allowing the device to be discovered by Visual Studio.
I had Productivity Power Tools (PPT) installed on my Visual Studio 2012 for quite some time and everything was working well. Suddenly, it stopped working and I noticed it got disabled under Extensions.
I cannot enable it (the Enable button is grayed out), only uninstall, but even uninstalling it and re-installing it didn't do the trick!
I also installed VS 2013 Community (the new full free version) and installed PPT on it and the situation is exactly the same.
Check it!
Tools - Options - Environment - Extension Manager - Load per user extensions...
Worked for me.
After researching this issue inside out (and vise versa), I have finally found out the reason for the mess described in the question here (at least for my specific case):
It appeared that I had a few versions of Visual Studio installed on my PC, which is obviously a very unhealthy situation to have. In my case, the only symptom for this kind of "sick" diversity that I have noticed was the problem with the extension. And a good thing that happened...
I just uninstalled ALL the versions I had installed on my PC and re-installed only the version (one of them) I wanted to continue working with (in my case, VS2013 Community).
I re-installed all the desired extensions, including of course the Productivity Power Tools, and everything is working just fine.
Of course, rebooting the system between installs wouldn't hurt...
After all, I am talking about a Windows-based PC. ;-)
Everything was going fine but the next day, when I opened the visual studio It showed error as
this error occur at every project files and at the starting.
I uninstalled and reinstalled the VS again but also nothing is improved. when I started my pc in safemode , in that case visual studio runs fine however when I opened in normal mode , It shows the error.
Also using command like devenv or devenv/safemode or devenv/resetsettings pops the same error message.
In my experience and from what I've heard from others, VS2005 has problems on newer OS's and needs to be run in a XP VM for reliable results. Some editions of Win7 have a nice transparent way of doing that for software that doesn't like newer OS's, but the VM component needs to be installed first.
I also recall VS getting fouled and needing to be ripped out and re-installed to work again. In your case, re-installing from original media did not include all the service packs and patches, and it probably only worked at all due to updates and a bit of luck. You might try restoring from a backup rather than re-installing, but it's really a lost cause.
I'm trying to install Visual Studio 2005 on a Windows 7 box but am repeatedly getting the same error. When I run the installer it starts to run then pops up with a message saying:
"A problem has been encountered while loading the setup components. Canceling setup."
Various suggestions has said that maybe the install is corrupted so I downloaded a fresh copy of the ISO from MSDN today, same issue. Another suggestion is that installing from the ISO may be the issue so I extracted the contents of the ISO to a folder on my HDD, same issue. I have also tried running the files as administrator and in XP compatability mode, same issue.
Searching for this issue the most common responses I've found have been about installing SP1, however I cannot get the base product to install and therefore cannot apply SP1.
Does anyone have any further suggestions as to what I can do to fix this issue and get VS2005 installed? If anyone wants any log files of any variety I am happy to supply so long as you tell me where to look as I'm not sure.
As for why I am using VS2005 and not a newer product, it is required for the ongoing support and maintenance of some older applications we manage. These cannot be easily migrated to a newer version of Visual Studio without some considerable investment of time and that would probably be longer than the time it will take to develop newer, replacement applications (which is currently in progress). Until the new applications are available though we need to maintain an environment to use.
Did you try running setup.exe in compatibility mode with Windows XP? Some discussion here on how to do this.
Another alternative since you alluded to having an MSDN subscription. Download Windows XP and install it into a VM. (If HyperV isn't already in installed with your Win7, you can add it from Control Panel->Programs&Features->Turn Windows Features on/off). Then install VS2005 from there.