Home/ Questions/Q 6048979
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T07:31:27+00:00

We’re working on creating a specialized graphical editor for our enterprise applications. We’ve looked

  • 0

We’re working on creating a specialized graphical editor for our enterprise applications. We’ve looked at and rejected DSLs. Ideally I’d like to have the main interface of the editor be docked like the code windows and use WPF for drawing. Can anyone point me to some documentation to get me on the right path?

Thanks.

Colin.

UPDATE: It’s beginning to look like “no.” From http://msdn.microsoft.com/en-us/library/bb166228.aspx: “Document windows are created by implementing an editor. The IVsEditorFactory interface creates document windows as part of instantiating an editor. For more information, see Accessing the Editor By Using Legacy Interfaces.”

Following the link to http://msdn.microsoft.com/en-us/library/dd885127.aspx gives this this bit of advice: “You can access the Visual Studio editor from legacy interfaces. The Visual Studio SDK includes adapters known as shims, which enable these interfaces to interact with the new editor. Nevertheless, we recommend that you update your legacy code to use the new editor API. Your code will perform better and you can use new technologies such as the Windows Presentation Foundation (WPF) and the Managed Extensibility Framework (MEF).”

So, to sum up: if you want to implement an editor you have to use the legacy interfaces, but you shouldn’t use the legacy interfaces because then you can’t use WPF or MEF.

Seriously Microsoft, WTF?

UPDATE 2: Now that I have the proper names (“custom editor”), I was able to find the following topic: http://social.msdn.microsoft.com/Forums/en-US/vsxprerelease/thread/9e605d0f-1296-47c9-a534-e54905251ebe

I still don’t see why they couldn’t have included that somewhere prominent in the MSDN docs. You know, like somewhere near where they tell you that you can’t use WPF if you’re using the legacy interfaces.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Creating a custom editor doesn’t have to be terribly painful. Yes, a custom editor will require implementing a few interfaces, but you can still use WPF to actually create the control that is hosted in the VS document frame.

    DiveDeeper’s blog has some great resources for learning about creating a custom editor.

    I’d recommend using a library like VSXtra to do a lot of the work for you. It will provide you with a nice base implementation of an editor factory, editor pane, package, etc. Istvan Novak writes about building a custom editor with his VSXtra library in this blog post.

    • 0