I just installed Windows 8 and Visual Studio 2012. Now I want to create a Windows store app.
But every time I try to get the developer license everything freezes...
Example PowerShell:
Show-WindowsDeveloperLicenseRegistration
Dialog "Accept"
Login
Dialog "getting license" (I use the german version, so the message could be different)
The dialog closes, the PowerShell Console is still frozen
The same thing happens in Visual Studio (background process not responding). Any idea?
I searched a few hours but the only solution I found was to remove Visual Studio and reinstall it completely...
Related
I'm trying to open a project from TFS 2018 (on-premises installation but I guess that would happen with any version or VSTS as well) dashboard but I can't.
I click on url Open in Visual Studio:
And an error form shows up:
The error description says:
Input args:/openurivsweb://vs/Product=Visual_Studio&EncFormat=UTF8&tfslink=dnN0ZnM6Ly8vRnJhbWV3b3JrL1RlYW1Qcm9qZWN0L2I1MjI0OWRjLTdhMDUtNDI1Yi1iZTE5LWNmMDM5YzE1YTJlND91cmw9aHR0cHM6Ly90ZnMubWFucG93ZXIuaXQvTmV4dEcv
Exception thrown:'Microsoft.VisualStudio.VSWebHandler.VSWebHandlerException'.
I have installed both VS2012 and 2017.
I tried also this workaround, but with no success:
Launch Developer Command Prompt for VS 2017 as Administrator
Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
Launch command: gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll
In the Windows Default Apps panel open the protocol handlers and scroll down to the vsweb: and the vstfs: protocol handlers. It could have multiple instances of the handler, one of which has to have the 2017 icon. Mine is showing 2 2017 icons because I have the 2017 preview installed side by side.
Change the default, restart the browser and try again.
In addition to jessehouwing answer, that works for Windows Metro UI systems (8 and superiors), this is what you need for Windows 7.
Go to Control Panel, select Default Programs and click the second option:
Then it opens the window where you have to change the association between Visual Studio Web Handler Selector and TFS Procotol Handler (vstfs:):
From the icon, as suggested, you can see that's Visual Studio 2012 symbol.
Now we change it:
Sorry bout Italian language, but procedure would be the same with any localization.
This happened to me several times in a row today. I pressed F5 to Debug my Windows Azure project in Visual Studio 2013 with the emulators, and the project would build, but no browser launched. There was no build error either, it would just complete the build and look like it was ready to launch a browser, but then just stop.
Finally I saw a message in the bottom left status bar of Visual Studio that said "Compute emulator shutdown". Then I moused over the Azure icon in my taskbar, and it said "Storage Emulator is started", but "Compute Emulator is shutdown".
I was helped by this post that mentioned where the emulator log files were. The key log file I needed was
C:\Users[User]\AppData\Local\dftmp\EmulatorRuntimeLogs\ErrorRuntime.log
That log file had an error in it about failing to write a file. This reminded me that I had forgotten to start Visual Studio as Administrator. Its a simple step for any Azure project but something that I forget to do sometimes since the majority of projects that I work on in Visual Studio are not Azure projects. And I didn't see this specific failure case mentioned in Stack Overflow, so thought I would post it.
I closed Visual Studio, right-clicked on the Visual Studio 2013 launch icon, chose "Run as Administrator", and then browser launched fine when Debugging
My need
Currently I have to open Visual Studio to make a get latest or a commit pending changes.
I want to do that the same way with TortoiseSVN right in Windows Explorer.
What I have tried
I made google research and comes down to using the tool called TFS 2012 Power Tools
Someone also mentioned about this issue here
Though after installed, I got nothing working as espected. Wondering did I do wrong then...
I'm using Windows 8.1 and Visual Studio 2012 Web Express.
Question
How should I do to install it properly and get it work after all then?
Assuming that when you installed the power tools you enabled shell integration and then logged out/back in to active them, then you need to do a few things:
Do an initial 'get' from TFS using Visual Studio Team Explorer and make a note of your workspace folder.
In Windows Explorer, right click that workspace folder. You should see the context menu items appear.
Most people having trouble with the context menu appearing have forgotten that to log out and log back in, as Windows Explorer needs to be restarted to pick up the new shell extension.
My copy of Visual Studio 2012 is instable. It starts up and I can load projects, compile and run them. But from time to time it crashes randomly. It now also crashes when I try to add a new windows form to a project. But the crashes are independent from the project loaded.
My first idea was to install all new updates but if I go to the updates & extensions section it opens the dialog box and crashes 1 second afterwards. I then thought I might deinstall it and reinstall VS 2012 or 2013. But I also cannot deinstall it. If I go to windows programs to deinstall it I can click on the change button, but after this the installation program crashes. I also tried to download the VS 2013 preview and install it but this also crashes before showing a dialog box of window.
So I don't know how to proceed. Does anybody else have similar problems?
Try running Visual Studio in Safemode (devenv /safemode) or run it with logging turned on (devenv /log) the logs will be written to a folder in your user profile. Also check the Eventlog to see whether there's a error report. There should be 2 events logged when Visual Studio crashes. One "Application Error" and one ".NET Runtime Error". The latter will provide information about the stack trace that causes the crash:
When you try to uninstall Visual Studio, first remove update 1, 2 or 3, then repair or remove the whole thing. If uninstall fails, i'm afraid you'll need repave the machine to get it back in a supportable state. When you uninstall an update, you always need to repair Visual Studio itself before re-applying the updates.
Try removing all addins (Resharper, NDepend, etc) and extensions (either from the Visual Studio Updates and Extensions window or by deleting them from the Visual Studio or User profile folder).
Try resetting settings and add-in settings (devenv /ResetSettings) and (devenv /ResetSkipPkgs), try rebuilding all templates (devenv /setup).
You can even attach one Visual Studio instance as a debugger for the other to see where the exception occurs. Sometimes it can give you valuable information, sometimes the crash just doesn't happen because the actual issue is timing related.
If all else fails, open a support call with Microsoft, file a bug on Connect or do a clean re-install of your system.
Judging from you Error message you're running the Visual Studio 2012 Web Developer Express edition, instead of devenv, try wdexpress from a normal (windows) commandline window.
Another common issue that can make Visual Studio very unstable, is a corruption of the Add-in cache. Clearing it will trigger Visual Studio to rebuild it for you.
I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.