Visual Studio Word WebAddin won't load - ms-word

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.

Related

Not able to see Share point add in Visual Studio 2017

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.

Does VSCode have a different view in mac and in windows?

I am beginner programmer and have just installed VSCode. But to way VSCode looks in the tutorials is different from the one I have.
I mean the Left most and the Topmost looks different.
So I cant flow the tutorial and almost all tutorials has the same look.
The links of the sreenshots are down below:
Is my version older or it looks like that on windows or anything else, please explain step-by-step cause I am new to this. Thanks a lot!
Sorry if it is a bad Question!
You installed Visual Studio which is a more powerful IDE from Microsoft. Don't confuse it with the editor Visual Studio Code.
There is an answer explaining the main differences between the environments: https://stackoverflow.com/a/33798601/10770079
Visual Studio (full version) is a "full-featured" and "convenient" development environment.
Visual Studio (free "Express" versions - only until 2017) are feature-centered and simplified versions of the full version. Feature-centered meaning that there are different versions (Visual Studio Web Developer, Visual Studio C#, etc.) depending on your goal.
Visual Studio (free Community edition - since 2015) is a simplified version of the full version and replaces the separated express editions used before 2015.
Visual Studio Code (VSCode) is a cross-platform (Linux, Mac OS, Windows) editor that can be extended with plugins to your needs.
You downloaded Visual Studio the IDE.
Visual Studio Code is a pseudo-IDE style text editor.
Be sure you look up specifically Visual Studio Code Download for [ insert operating system here ].

Deploy Acumatica Framework Tools fails

I am trying to Deploy Acumatica Framework Tools using the Framework Configuration Wizard and I getting the following error:
Exception occurred while installing resources.
Inner Exception:
Can't find the Visual Studio template items location.
I have Visual Studio 2017 Enterprise running on Windows 10 Pro. Both are up to date.
Any ideas on how to correct this. I’m going to the Acumatica Summit next week and need to do the T100 and T200 course.
Thanks
Tom
The wizard is likely looking for the VS2015 registry folder. Until installers are fixed to check in the VS2017 location I recommend you create the VS2015 registry folders with these 4 dummy string keys pointing to VS2017 folder.
The key values in the picture below point to the default VS2017 folders. I tested this workaround a couple months ago on a colleague computer and we experience no ill effects:
I faced the same problem, but I could not change my registry due to company policy. My regedit.exe was unavailable:
So, to fix this issue I installed Visual Studio 2015 Community Edition .
That fixed the issue.
Do not forget to restart your computer after installation, otherwise - you will get the same error. If you solve this problem with installation of VS2015, you will be able to use Visual Studio Template
in VS2015 only. It will not be available in other versions of Visual Studio.

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.

using NuGet with Visual Studio 2005

What would be the most frictionless workflow for working with NuGet and Visual Studio 2005? Is this at all possible? I understand that the plugin is only available for Visual Studio 2010, but there is still the package manager console wich seems to be nothing more than powershell. Can I run the console without Visual Studio and can the console download and integrate packages into visual studio 2005 projects? If so, how is this done?
Scott Hanselman blogged about adding NuGet "support" to Visual Studio 2008. You can probably adapt this slightly to work in Visual Studio 2005 too, though of course you won't get the same experience as in Visual Studio 2010.
Well, not really. A better title would be "How to Cobble Together
NuGet Support for Visual Studio 2008 with External Tools and a
Prayer." The point is, there are lots of folks using Visual Studio
2008 who would like NuGet support. I'm exploring this area and there's
a half-dozen ways to make it happen, some difficult and some less so.
The idea would be to enable some things with minimal effort. It'll be
interesting to see if there are folks in the community who think this
is important enough to actually make it happen. Of course, the easiest
thing is to just use 2010 as it sill supports .NET 2.0, 3.0, 3.5, and
4, but not everyone can upgrade.
Someone could:
Backport the existing NuGet Package References dialog to 2008 using
that version's native extensions (not VSiX)
Create MEF (Managed
Extensibility Framework) plugins for the nuget.exe command-line to
update the references in a vbproj or csproj
Use PowerShell scripts and
batch files to get the most basic stuff working (get a package and
update references.)
Maybe write a shim to get DTE automation
working...
But that's coulds and maybes. Let's talk about the MacGyver
solution. more »