Not able to see Share point add in Visual Studio 2017 - visual-studio-code

I have just started exploring Visual Studio code. I have installed VS 2017 , and i want to create a Share point project. But I cannot see Share point Add-In in installed or Online section.
Can any one please help

According to this article, this could be your problem:
This issue occurs because of the Office Developer Tools for Visual Studio 2017 is not installed.
You would have to add the extension using the Visual Studio installer.

Related

How to install AJAX Control Toolkit in visual studio 2022?

I have Visual Studio 2022. I want to install ajax control toolkit, but the 20.1.0 installer does not work from the devexpress. Is there a way to get it working?
I had the same problem.
This is what I did as a workaround:
I installed Visual Studio 2019 Community edition on my system. I got my copy through https://visualstudio.microsoft.com/subscriptions/. It may be available at other sites as well.
Then download and install AJAX toolkit from DevExpress. It will now install properly and include the AJAX toolkit controls in the Visual Studio 2019 toolbox. It WILL NOT include the new controls in the Visual Studio 2022 toolbox.
To include the new controls in the Visual Studio 2022 toolbox, follow the instructions at add ajaxtoolkit to toolbox
This workaround has worked for me so far.
I hope it works for you!

Visual Studio Word WebAddin won't load

I am trying to make the Word Web Addin project template (that came with Visual Studio) to work. When starting the project, without modifying anything, I am stuck with the following message :
I have no clue how to troubleshoot this. I've searched on google but most stuff with Visual Studio is about VSTO solutions which is not the case here. Tried both VS2017 and VS2019 with no luck.
Any ideas how to investigate this ?
btw: I'm on Windows version 10.0.14393 with office 2019 / Word version 1911.
Can't tell why but after updating my Visual Studio without success, I made a "repair" installation of my VS2019 and it finally worked.

Visual Studio 2017 and project from GitHub or Visual Studio Team Services

I have several projects on GitHub and on Visual Studio Team Services. In VS 2015 I simply connected to a server, selected and connected to a project. In Team Explorer I saw all solutions in Solution part. In Visual Studio 2017 I don't see any solution. If I check it again in VS 2015 (on the same computer), it works fine. Is there something more to do in VS 2017 to see the solutions in Solutions part?
You appear to be using TFVC for this example.
Have you defined a workspace – or at least looked at the workspace in Source Code Explorer – so VS2017 knows you have the local files?
(AIUI the solutions list is based on a search of the local workspace.)
Tried to find where I read this yesterday but I can't remember, but according to Microsoft on the developer forums, this is as intended. You need to click "show folder view" to see your solution.

Can I use source control from Visual Studio Team Services using VS 2015 Community edition

I want to install Visual Studio Community edition and I need to use Visual Studio Team Services (was Visual Studio Online) free account as source control.
The information on the visual studio site seems to indicate no functionality available under the Team Foundation section. But from a lot of searching online I have found conflicting advice and people say that they have been able to use it with an in-house TFS etc.
Can I use the Visual Studio 2015 Community Edition with the Visual studio Team Services free services like source control, work item tracing, branching/merging code etc?
The answer is YES. You can use any VS edition to connect to Visual Studio Team Service.

VS 2013 CodeLens

When I open a project from the Visual Studio Team Services (scrum 3 template) I only get the CodeLens reference count. Is this a bug in VS? Why do I not have CodeLens with full TFS versioning Comments, Edited By, etc.?
FYI: I have enabled all options in Visual Studio Tools > Options > CodeLens.
I also tried the following with no success:
Create a new project in Visual Studio Team Services.
Disable and re-enable CodeLens.
There is an update!
Currently CodeLens is being developed for Visual Studio Team Services, currently in Public Preview for what I have read so far, in US and West-Europe.
Requirements:
Be using Visual Studio Ultimate 2013 Update 4, or Visual Studio 2015
(Preview or later version).
Check your code into Team Foundation
Version Control in Visual Studio Team Services.
Just updated to VS Ultimate Update 4, already had a solution setup on Visual Studio Team Services, works great as expected.
troubleshoot, CodeLens not appearing?
Close all Visual Studio Instances.
Remove the cache from %localappdata%\Microsoft\VisualStudio Services\5.0\
Reopen Visual Studio, open the solution from Visual Studio Team Services.
I'm not sure if it was necessary to do this for me, I did it, looked like it had no effect and the codeLens still didn't appear. While I was typing out a new question they suddenly appeared. So it could take a few minutes.
Source: CodeLens in Visual Studio Team Services is now in public preview
For Visual Studio 2015: Should be available by default. Source. I'm using Visual Studio 2015 Enterprise and it works good, even more then in visual studio 2013.
As DaveShaw answered, TFS 2013 is required, but I still had problems after installing TFS 2013. Turns out you need to have CodeIndexing enabled on the TFS Server. My codeindexing was on, but I think the index was corrupted somehow and I had to reindex it.
This is a good link (go to the Q&A section at the bottom):
http://msdn.microsoft.com/en-us/library/vstudio/dn269218%28v=vs.120%29.aspx
Here is the TFSConfig CodeIndex syntax:
http://msdn.microsoft.com/en-us/library/vstudio/dn280925(v=vs.120).aspx
Once you get your codeindex running, you have to do a get latest from Visual Studio and then your codelens should work.
Server-side CodeLens indexing is not currently supported by the Visual Studio Team Services, only on-premises TFS. This is partly because of the potentially unbounded number of tenant accounts in the online service, each with its own background job to do the indexing of changesets. However this could change in the future.
Source: I worked on CodeLens.