I have VS 2012, 2015, & 2017 installed on my machine. We also have TFS 2017 locally installed. When I get an email for a code review and click the link, for everyone else it opens up VS 2015/2017 depending on the version the other people have. For me it opens VS 2012 but fails to open up the code review. I noticed if I copy and paste that vstfs//codereview/request/... link in IE it prompts me to open an external application. In this prompt it says:
Do you want to allow this website to open a program on your computer? It then shows Program: Vs 2012 and Address: vstfs:///.... For other people under the Program setting it shows the VS selector and not a specific version.
Does anyone know where I can change this setting to use the VS selector program vs VS 2012 with this vstfs:// protocol link?
Go to the Windows settings (Default App Settings in Windows 10).
Choose Default Apps By Protocol at the bottom of the screen.
Find the VSTS/TFS protocol handler. Set it to the Visual Studio web protocol handler.
You'll have to pick the right version by the icon (if multiple are registered). Unfortunately, the title doesn't contain the version number.
Related
I have built an add-in which works fine in Excel online, whereas it does not work in Excel 2016 for Windows.
I know that in Windows 10, we could use this tool to debug the add-in, however I am using Windows 7.
I just installed Visual Studio 2017, right clicking on the add-in shows a menu where Attach Debugger is. But clicking on Attach Debugger fires nothing.
Does anyone know how to debug in this case?
Two potential options:
You can use Volorn.js to remotely debug your add-in. You can use the Debug Office Add-ins on iPad and Mac article as a starting point. Although this article is targeting Mac and iPad, the concepts are the same for Windows.
You can also use Visual Studio by creating a new Excel Web Add-in. Simply replace the default manifest with your own. Note that you still need to retain the default web site, Visual Studio still this for some library references. It will use your manifest's URL for the source location however.
Office applications use Internet Explorer for the web browser, so all settings from IE should carry over. I have found that if you disable (uncheck) both the Disable script debugging (Internet Explorer) and Disable script debugging (Other) options, your debugger breakpoints will be hit (I tested this in Outlook 2016).
You will need add debugger; statements to the source code to add breakpoints. When these statements are hit, a dialog like this should appear:
Simply select 'Yes' and a new instance of visual studio should open, with the debugger attached to your script.
Switching from Visual Studio 2015 to 2017 I find that launching a Web API project now starts a clean, separate Chrome window. For the most part I like that, and I certainly like the idea, however: this also means extensions are missing in Chrome.
Is there a way to start a Web API project from Visual Studio 2017 and have Chrome launch with extensions enabled?
Or, failing that, could I revert back to the old behavior where my project is opened as a fresh tab in my existing Chrome window?
I've tried Googling but found nothing. I checked the dropdown in Visual Studio with browsers (and checked the "Browse With..." dialog) but found no solution there either.
All you need to do is to sign-in to the instance of Chrome that VS2017 launches as the user you have all your usual extensions installed under (i.e. sign-in as the same user you usually sign-in as).
This sign-in "sticks", so extensions will load in the current - and all subsequent - debugging sessions.
You can revert back to the old behavior by
Debug > Options > Debugging > General > (uncheck) Enable JavaScript debugging for ASP.Net (Chrome and IE).
Is there a way to start a Web API project from Visual Studio 2017 and have Chrome launch with extensions enabled?
Yes, but it works for one project only, mean you need to re-install extensions when you launch a brand new project. I tried Sync in Chrome (not work).
In my opinion, there are something to do with Chrome remote debugging protocol profile. I hope someone knows about Chrome can give a final solution for this.
you can study more here: remote debugging protocol
There is a way that you no need to change anything. But it annoying.
Because Visual Studio 2017 use an instance of Chrome for debug mode when you hit F5, so you can leave that debug mode instance with remote debugging protocol open, and use your default Chrome instance with full extensions. Just copy and paste the link into your favorite Chrome instance.
Cheer! hope it help.
I have bought UnityVS and it was working well with VS2010. Later Microsoft aquiared their company and now UnityVS is a free plugin with one difference: it is much more unstable.
I had several issues with new updates and finally I decided the move to completely new version which is called "Visual Studio Tools for Unity" instead of UnityVS.
I am using Microsoft Visual Studio Community Edition 2013 Update 4 (which is actually a VS Professional). Everything looks good but it attached to the process because the plug icon on lower right corner tells me it is attached to Unity Editor (My version of Unity Editor is 4.5.5f1). However when I click on "Attach to unity" button it only compiles and then does nothing (it doesn't lock). As a result I am unable to debug because it doesn't hit any breakpoint.
Please somebody help me because even their support page doesn't show any useful link to talk with them (It is Microsoft anyways!)
After several hours I found a solution! The only this I did was to double click on the plug icon in lower right corner of visual studio and clicked on the custom IP and then instead of 192.168.0.xxx (My IP) I entered 127.0.0.1 and for the port I used the port that is shown already for the unity instance. That's it. :)
I have installed and registered Visual Studio 2010 Premium (+SP1) onto the Windows XP Mode VM within Win 7 Pro; I have applied all of the product updates also. I have not yet created any projects as my first task was to try and connect to our TFS 2013 Server.
My problem is that from within Visual Studio 2010 whenever I try to "Connect To Team Foundation Server" from either the Start Page; The 'Team' Menu drop down or the icon in the Team Explorer tab, the window to "Connect To Team Project" flashes up and immediately closes and so I cannot enter the details of my TFS server.
I cannot find any errors 'Event Viewer' and there is no further information from Visual Studio. It cannot be the TFS setup as I haven't got that far yet.
It looks like XP mode is interfering. Not all applications are supported and I have never seen or used visual studio in this manor.
You would be better either running VS2010 on your local Windows 7 or running it in a VM (Not in XP mode).
I found a solution to this and it is somewhat unbelievable, but it definitely worked for me:
Ensure HKEY_CURRENT_USER\Software\Policies\Microsoft\Internet Explorer\Control Panel\Colors = 0
Go to Internet Properties -> General -> Colors
Change the check state of 'Use Windows Colors' and change the check state back again then click OK and click OK on the internet Properties page.
My "Connect To Team Project" window now stays open allowing me to select a server!
A colleague enlightened me to this trick which is regularly used for Win 7 installations but this is the first XP version (although it is the Win7 XP Mode VM).
This works to fix flashing pop up screens for Win7 & XP and has been reported to MS.
I have a project on vs 2010. I have tried to add project on windows server 2003 which has tfs 2010 installed. Later on I have switched to windows server 2008 and then installed tfs 2010 again. But I have changed server name.
Now, when I try to add project to tfs, I receive and error says that;
Team Foundation services are not available from server http://old server name:8080/tfs/. Technical information (for administrator): The remote name could not be resolved: 'old server name'
I have tried to add different projects but I havent received any errors. I am thinking problem is like, visual studio installed on my client computer has registered project with old server name and still tries the same server but team explorer can not find the server.
what shall I do?
PS: I am not tring to get my codes on old server. I did not use tfs, just wanted to learn it.
If you get the message when you open Visual Studio then you need to go to Team Explorer and click the "Connect to Team Project" button, then click on the "servers" button and remove the old server. If you need to you can also add the new server here.
If it's when you're opening the solution then you need to remove the Source Control bindings
open the solution and then go to "File", "Source Control", "Change Source Control" this will open up a screen where you can Unbind the Projects and Solutions from the old server.