How can I populate Intellisense with DotNetProjectResolver?

SyntaxEditor .NET Languages Add-on for WPF Forum

Posted 9 years ago by Craig - Varigence, Inc.
Version: 11.1.0541
Avatar
We have a C# editor that's been using the WinForms syntax editor and we want to migrate it to the WPF Syntax Editor. To display intellisense, we're using the DotNetProjectResolver and assigning it to our WPF SyntaxEditor's Document.LanguageData property. So, like this:

public CodeEditor()
{
        InitializeComponent();

        _dotNetProjectResolver = new DotNetProjectResolver();
        _dotNetProjectResolver.CachePath = Path.Combine(Path.GetTempPath(), "MistScriptEditorCache");
        wpfSyntaxEditor.Document.LanguageData = _dotNetProjectResolver;
}
For each C# file in our project's collection, we do:

public CodeEditor()
{
_dotNetProjectResolver.SourceProjectContent.LoadForCode(new ActiproSoftware.SyntaxEditor.Addons.CSharp.CSharpSyntaxLanguage(), file.Path, file.Contents);
We also add various assembly references to the resolver.

While I understand that the .net languages add-on doesn't have built-in intellisense support yet, is there a way we can leverage the project resolver with the wpf syntax editor so we can use it to display intellisense?

Once Intellisense is available in the add-on, will we still need the resolver or will there be a different way to handle this scenario?

Thanks,

-Craig

Comments (1)

Posted 9 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Hi Craig,

Sorry the WPF SyntaxEditor add-on doesn't know anything about how to use the WinForms' DotNetProjectResolver so what you did won't do any good.

For the next-gen platform of the .NET Languages Add-on in WPF/Silverlight, we're doing a brand new design for the reflection data from scratch that will address shortcomings with the WinForms version and also be easier to use in general. We've started on its design and will be working on implementation in the coming weeks. Keep an eye on our blog for details.

So yes there still will be an equivalent of the DotNetProjectResolver in the newer design since we need to know what assemblies and source files are part of the same "project". However in the newer design it's likely that this piece will be a service you register on your language.


Actipro Software Support

The latest build of this product (v2019.1 build 0683) was released 13 days ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.