I have installed the VSProlog extension in my Visual Studio 2015, from here: https://visualstudiogallery.msdn.microsoft.com/50f0f293-bcb5-4f95-a9d0-afff92306973
Going to Tools>Extensions and updates I can see the extension installed, and it's enabled. Everything seems fine.
But trying to create a simple prolog .pl or .ari file, in File>New project... I can create C#, Visual Basic files, ASP, Python... but nothing appears related to Prolog.
How can I create a Prolog File in my Visual Studio?
Disclaimer: I'm the developer of the extension.
As stated before, VSProlog is not a template extension. It just enables syntax coloring for prolog files defined as *.ari and *.pl.
Opening a .pl file with Visual Studio and the extension installed (of course) should be enough.
Feel free to file an issue at GitHub
Related
I used to code on Visual Studio Code. Now, i'm trying to learn how to code on Visual Studio 2017 as it will be more beneficial for me. So far, it's so good.
But there is one thing which i miss on VS which is, in VSC, there was a neat extension, called Path Intellisense which autocompleted (or showed suggestions for) ./../file style file-paths. While coding in javascript (ExpressJS to be exact) i got no suggestions for file path autocomplete. Also, i didnt get any extensions to do so.
Those dot style file paths confuse me and i would really like an extension, or a workaround, in VS to help me with that. Are there any extensions for this?
E.g.
I have Visual studio 2013 Ultimate, and want to use typescript. I installed the plug-in:
http://www.microsoft.com/en-us/download/details.aspx?id=34790
It didn't show any errors during or after the install. When I started VS2013 again and went to File > New > Project, there was a TypeScript thing in the templates. But it said "Install the latest TypeScript for Visual Studio", and trying to create such a 'project' results in a "project creation failed" message.
I also tried making a new file, but there was nothing related to typescript. Making a new file and changing the extension to .ts didn't work either (the icon of the file shows that it's an unknown filetype).
How do I get typescript to work in VS2013?
EDIT: I noticed that there's no typescript listed in de list of installed extensions. Could it be that the plug-in didn't detect my VS2013?
Answering my own question based on the comments on the question and own experiences. For when other people find this question.
It helps to restart your computer after installing the typescript plug-in.
And the Web Essensials 2013 plug-in doesn't mix well with typescript, so disable that to avoid Visual Studio crashing. (credit to Ken Smith; see comments on question).
i'm searching for a way to change the language of the "Spell Checker"-Extension for Visual Studio 2010.
The problem is following:
I'm using the german language version of Visual Studio 2010. If I use the "Spell Checker"-Extension it checks the correctness in german language, while I'm coding in english.
So nearly every single word is underlinded as incorrect.
How can I change the checking language to english or how can I change the libary it used to check language?
Any Ideas?
I found a solution for the problem by myself.
If anybody like to know it:
First download the extension inside the Visual Studio extension-manager.
Second download the source of the extension and open it in Visual Studio (Visual Studio SDK has to be installed to open the project)
Third navigate to Spellchecker/Spelling/SpellingTaggers.cs and add the following line inside the CheckSpellings method of SpellingTaggers class under the textBox initialization:
textBox.Language = XmlLanguage.GetLanguage("en-US");
Next build the dll-Files with Visual Studio
And finally replace the dll-files with those in the directory of the Spell Checker Extension (it can be found under %HOME%\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Roman Golovin, Michael Lehenbauer, Noah Richards\Spell Checker\2.23 or something similar)
That's it!
If you want to use a language different from "en-US", change the Language Code.
There is a fork of spellchecker, that maybe will eventually be integrated into the main branch, that supports spellchecking in multiple languages here:
https://github.com/simonegli8/Spellchecker
Simon Egli
Remark:
Step 5 will not work in all cases. I think dlls are cached or something like this, so it would be better to uninstall spell checker from Visual Studio and reinstall the new compiled version of SpellChecker.vsix (could be found in SpellChecker.Implementation\bin...).
This worked for me.
A program we work with in my office can be automated through VBScript Files, yet the files are saved with an extension *.RVB other then *.VBS. I'd like to use Visual Studio as my editor/debugger, which is working. Yet it is not coloring the code like it does if I have a *.VBS file open.
Under Tools->Options->File Extension I added "RVB" and set it's editor to Microsoft Visual Basic, yet it is still not applying any syntax highlighting to my file. What am I missing?
I realize this might be beyond what you had in mind. However, I see no acknowledgement to your solution so I am going out on a limb here. You could create a language extension and totally control all aspects of the coloring. This is easily transfered to 2010 (the example is in 2008) but remains relevant.
http://msdn.microsoft.com/en-us/vstudio/bb851701
In this video, Hilton Giesenow illustrates a simple working Language Service. He begins by building a simple scanner colorizingsing based on regular expressions, then expands on this to implement the Managed Babel framework, integrating MPLex and MPPG directly into the Visual Studio build as well.
I've tried to install this
http://www.thinktecture.com/resourcearchive/tools-and-software/wscf
it seems I have to download the vs2005 version first and then update with a file for vs2008.
But the addin failed to install as for me.
Did someone achieve to do so with VS 2008 ?
You're right. It looks like it is needed to have VS 2K5 before being able to use this add-in.
I guess the setup for VS 2005 tries to add a toolbar or some menu items, so it launches VS 2005, which of course fails if you don't have it.
Instead of preparing a setup program for VS 2008, the author just provides an updated .addin while for it.
Maybe it is enough to extract the files from the .msi (see the back room tech for a link) and then install the .addin file from the zip of the "2008 version".
If you succeed in doing this with the msi, put then this .addin file in a directory where VS 2008 looks for it (see the list in Tools / options / Environment / Addins Macro security).
Inside the .addin, there is the path to the add-in itself, which must be of course adapted.