i working with Visual Studio 2022 CE and use a Cherry Steam keyboard, last have add-on keys for lock, calc, mail and browser.
The browser-key open normally the default-browser (example opera or edge), not so in visual studio.
In VS open a browser-tab with default Microsoft page -> vs are crashed :(
How is the way to deactivate this "shortcut" in VS?
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.
Hy All!
I try to develop some application for Windows Phone, but I have found some problems in my development environment. I've installed the Visual Studio 2012 Express for windows phone and Visual Studio 2013 Ultimate (with wp 8.0 SDK)
in the same time, If I make a project in "Visual Studio Express 2012 for Windws Phone" (I can make a simply Windows Phone app (I mean Visual C#/Windows Phone/Windows Phone App) )it works.. but if I try to upload on my phone it doesn't work well..
At the same time if I make a project in Visual Studio 2013 ( I can't make a same Windows Phone app(I mean "Visual C#/Store apps/Windows Phone Apps/Blank App(Windows Phone) ) In this project I can't use some namespaces e.g Windows.Forms. But I can upload the code on my phone( And If I tried the VS2012 projects I could upload them too)
I know for some reason the VS 2013 don't add the same references to the projects but I don't know why..
I tried to add the right references to VS13 projects but it doesn't work..
I think there is a solution but I don't know what.. Anybody?
If you're using Visual Studio 2012 and you want to open a project that was created in Visual Studio 2013, you might be able to customize the project system to incorporate features of Visual Studio 2013. For information about how to do this,this will help you, seeHow to: Modify a Project System So That Projects Load in Multiple Versions of Visual Studio.
I have VS 2012 and 2013 installed on my system.
I have a 2012 project that I want to get pulled up in VS 2013 when I double-click it from the Windows Explorer.
Is this possible?
If you only want specific slns to open in 2013, you can open the sln file in a text editor, and change the line
# Visual Studio 2012
to
# Visual Studio 2013
Note that it will ask you to upgrade the projects to 2013 when you open it for the first time. If you want all of 2013's compiler features you will have to upgrade, but if you chose not to it will still load in the 2013 IDE and you get some of the IDE related features.
Right click any solution file and select Open with... option. Use Visual Studio Version Selector as the default program to use for Visual Studio solution files.
It appears that it's no longer possible to debug using VS2012 tools on a Surface RT running 8.1 (see Debugging Surface RT 8.1 from Visual Studio 2012).
So, how can I uninstall it, because it still has icons on the start menu, and items under program files. The digital signature is no longer recognized, so it's not possible to uninstall via the control panel.
Just remove the program files folder of Visual Studio 11.
Then go to your registry keys in HKLM => Software => Microsoft and remove the Remote Debugger entry.
Now you can do a fresh install of the VS2013 remote debugger tools and next time you'll restart the old icon seems to be removed from the all apps screen.
Good luck :)
Yeah good luck with that, we will all need it... As is mentioned in a few places on the web, Win 8.1 and Visual Studio 2013 can develop apps ONLY for Windows 8.1, while Windows 8.0 and Visual Studio 2012 can develop apps ONLY for Windows 8.0... You can install both side-by-side on the same machine (VS 2012 and VS 2013) though.
But what really gets me is that my new surface 2 is now a paperweight because I can no longer debug on it as I don't wish to abandon Windows 8.0 development ATM. I hope Microsoft addresses this as it could become a serious fragmentation issue and keep developers away in droves.
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...