Open bmingles opened 9 years ago
Look for NitraGlobalConfig.xml file in Nitra installation diretory. You have to add section for your own language
<Language Name="MyLang" FileExtensions=".abc" Grammar="Parser.Class.Name" StartRule="StartRuleName">
<Module>C:\mylang\My.Lang.dll</Module>
</Language>
Unfortunately there is not support for environment variables in config.
Now we are completely redesign custom languages integration with VS, so this config will be dropped soon. Instead we are making tool (Nitra.LanguageCompiler.exe) that generates entire VS package project for custom language.
Sadly, I tried that and it still didn't work.
<Language Name="Perl" FileExtensions=".npl" Grammar="PerlNitraGrammar" StartRule="CompilationUnit">
<Module>C:\code\githome\PerlParser\PerlNitraGrammar\bin\Debug\PerlNitraGrammar.dll</Module>
</Language>
At present we are working on a new version of VS integration. Wait a bit and we will publish it.
Is this still true: "At present we are working on a new version of VS integration. Wait a bit and we will publish it" ?
I'm loving this project. I was able to start a new grammar that works fine in the Visualizer application, but I can't seem to get it to recognize my files in VS. The included .njson and .ncs grammars work fine.
I am running Nitra v0.1.1433.0 and have installed the extension in VS2013 update 4. Are there any known issues / workthroughs for editing new grammars in VS?