When working in visual studio I have discovered that the F1.F1Help shortcut now redirects me to a google search instead of the MSDN page. This is for all that I have tested (including pages I know exists like https://learn.microsoft.com/en-us/dotnet/api/system.collections.objectmodel.observablecollection-1?view=net-5.0).
I am running Visual Studio 2019 and have resharper installed. I am using the resharper key bindings but when I change back to C# 2005 I have the same issue. I also have tried reinstalling visual studio and repairing but I am in the same situation.
How can I debug or fix this issue?
I have installed Visual Studio 2019 to do some testing on our code base ready for migrating from Visual Studio 2017, I am also testing to ensure it plays nicely with our TFS system (currently TFS 2018 on premises).
It looks as though the Visual Studio Work Item Form is back! (VS 2017 dropped support for this in favour of opening Work Items in a web browser). I've not managed to find any information on this. I like the fact that we might have the option to work with Work Items in the VS IDE as well as the web browser, however its return introduces a few issues:
We use a custom MultiValue control that does have support for the VS 2019 Team Explorer (it last worked in VS 2015). Do you know where I can get hold of a MultiValue control that will work on the Work Item form in the VS 2019 Team Explorer?
Given that the MultiValue control isn't working I would like to continue working with Work Items in a browser. The VS 2019 Team Explorer seems to favour opening Work Items within the IDE, how can I open them in a browser from within the VS 2019 Team Explorer? Better still, how can I configure it to open in a browser by default?
Is there a better place for me to ask these questions?
Work Items should default to opening in the web in Visual Studio 2019. That behavior has not changed from Visual Studio 2017.
There is an option under "Tools->Options->Work Items" to enable the "Legacy experience (compatibility mode)". It sounds like that option has somehow gotten enabled in your installation. If you switch that back to "Default experience", work items should open in the web.
Hope this helps.
Sorry for the inconvenience. This is a designed behavior right now.
Please take a look at this similar issue: TFS work items opened inside Visual Study no longer open in the web browser, they always open in the Visual Studio editor
According to the response from MSFT:
We have re-design the default landing page for work items in Visual
Studio 2019 which only works with server >= 2019. If server is <
2019, work items will be open in Visual Studio only.
Since you are using TFS 2018 with VS2019, you may have to open work item in web portal from browser directly right now. Otherwise, you have to upgrade your TFS version from 2018 to Azure DevOps 2019, if you insist on opening the work item in Visual Studio.
I can't seem to find the Teams menu on 2019 Visual Studio.
Is it hidden or maybe an add-on?
Normally it is found on the main menu at the top. I have the Professional Edition.
I'm trying to open and edit an existing Angular 2 project in Visual Studio 2017 for Mac.
In VS 2017 for Windows you just do the "Open Folder" as i understand. However cant find the "open folder" in Vs2017 for Mac.
I have Visual Studio Code and it works fine, but had a plan to make a try with the vs 2017 for mac.
Reading the documentation it's not saying anything about spa, "just" xamarin and .Core projects so it may not be supported.
Maybe someone else have figured it out already?
Thanks
Greg
I installed Visual Studio 2012 Express for Web some time in early 2012, then I performed an update in mid 2013. Next, I started using the Orchard Content Management System. The problem is that IntelliSense is not working. When I open .cshtml files, I get no IntelliSense for inline server side code such as #Html. How do I get Razor IntelliSense working?
Uninstalling and reinstalling VS 2012 Express for Web is what worked for me.
Use Control Panel > Programs & Features to uninstall Visual Studio 2012 Express for Web.
Go to the download page to download and reinstall the most recent version.