.net - Overlapping alternatives for developing language support in Visual Studio -


i want develop support in visual studio particular language. mpf language services , mef editor extensions seem have awful lot of overlap, , have not been able clear answer on 1 should using.

i interested in developing language support in visual studio 2012 , later. working in c# , wish use managed apis only.

the msdn documentation states syntax highlighting should done language service. when go documentation there, there's note arguably suggesting use mef. when read mef documentation, doesn't specify designed handle full-file syntax highlighting; wording makes me feel intended interspersed highlight adornments.

on contrary this, however, ook! sample demonstrates believe full-file syntax highlighting, though sample of scale, it's not clear if suggesting should used way.

mpf language services seems have support adding filter save dialog. haven't seen language supported through mef, might have missed it. haven't found indication either of them support adding file type filter open dialog. suggests me mef editor extensions not intended implement full scale language extensions intended extend existing ones.

any thoughts, please?

edit:

some questions i'm hoping can answer directly:

  1. is mef editor extension point highlighting intended full-file syntax highlighting implementation, or intended interspersed adornments only?

  2. if have filetype , contenttype registered mef export, additional steps necessary (or possible?) cause associated file filter show in various file dialogs?

  3. are mef editor extension points intended replace , potentially deprecate mpf language services?

for full-featured support, won't able away using 1 thing. however, end combination of implementing mef interfaces , implementing of visual studio's core com interfaces. don't need use mpf language services package @ all.

i think question more broad intended, making difficult me write complete answer.

edit: new questions.

  1. you can use implementation of iclassifier full-file syntax highlighting. of newer visual studio-based ides use exclusively.

  2. you need export contenttypedefinition, not file type. posted blog article describing steps take register file types , extensions:

    file types , extensions in visual studio 2012

  3. maybe? more importantly, there things it's better @ , other things can't right now, pick balance best overall productivity.


Comments

Popular posts from this blog

node.js - Bad Request - node js ajax post -

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -