I'm using Microsoft Visual Studio Community Edition 2013. My trial ran out recently and I'm trying to renew it by logging in. A window pane comes up for me to sign in and I enter my credentials, however I get the following script error:
Line: 4
Char: 16405
Error: Object doesn't support this property or method
Code: 0
URL: https://app.vssps.visualstudio.com/_static/tfs/20150123T002517/_scripts/TFS/Loader.min.js
After some rudimentary searching, it seems as if I'm missing a library. Has anyone experienced the same problem and knows which part of the code it's referring to? I don't want to go on a mad updating rampage.
I have been running into this problem for months. I do development on Virtual Box machines running XP, because it is small and easy to copy, and I have gotten this problem on some of the machines and not others. I thought it had to do with window updates, but I have that turned off, and I am still getting the problem on machines that just worked a few days ago. Unfortunately with XP you can't update anything or even go back to a previous version of IE.
Actually, it was the virtualization software itself. I'm actually using vmware not virtualbox (mix-up in the comments). Incidentally, vmware just released an update today and after installing it, I was able to log in.
By the way, it could've been the log-in itself. After the update, microsoft visual studio didn't even ask me to validate the software, but went straight to the ide. I saw by my user id, an exclamation prompting me to sign in, whereupon I was able to validate my install.
Related
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.
This is weird. I installed Visual Studio 2013 Community Edition on two computers, with the same installer (and the installation started/finished around the same time) and there seems to be a problem with my licensing; one is activated and the other is... Locked, with no option to refresh or update.
After going through the installer and logging in, my first installation on my Windows 7 laptop went without any problem; it can run properly.
But when I finished installation on my Windows 8 laptop and logged in, I was presented with the following message:
Your license has expired.
Reason: Pre-release software.
[Insert image of the error screen]
I've tried reinstalling, and there seems to be no difference.Neither does logging out and back in (or logging out, restarting the computer then log back in) do any help in refreshing the license.
As for this question, it isn't asking me to upgrade any trial licenses; just a "you can't use this anymore message" and no option to refresh or "upgrade".
Note: Please give me a hot moment to gather the screenshots from my computers.
I had a similar issue. The way I solved it was to go to Control panel and try to uninstall it. When the dialog box appeared I pressed the Update (or Fix) button. After that, I rebooted and logged in and it worked.
My VS2013 was a trial version though so my license was expired but I was not able to pass the screen of the screenshot you posted.
Hope it works!
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 can't deploy applications to to my Windows Phone 8 device from Visual Studio Express 2012 anymore. I always get the following two lines in the console:
Deployment of application to device failed.
The interface is unknown.
The emulator also does not work anymore (xde.exe just crashes). All that worked once (Hyper-V is active).
All that happened without a change to my app (the same happens with a fresh hello world app).
The problem is not my phone, I tested a different phone (even different model), same problem.
I already completely removed and reinstalled the Phone SDK including Visual Studio.
The problem might have occurred since I updated to Windows 8.1 but I am not sure about this.
If anybody has a clue of what is going on here I would highly appreciate your help.
Since you've already tried removing/reinstalling VS and SDK, try creating a new user account on your Win8.1 box and running VS from that. If it works, the problem was probably some settings in CurrentUser registry hive, which Remove doesn't always clean up. Reinstall the already-installed VS and SDK may work better.
The 'interface' error means this is likely some COM issue, and that implicates registry. If you can figure out which DLL contains the interface, you may be able to fix it with (admin command line) > REGSVR32 <dllPath>. You can trace the registry accesses being made when you try to debug the app via SystemInternals ProcessMonitor
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.