Forums | NoesisGUI

Hey All,

We've recently upgraded our previous Noesis 3.X project to 4.0 to take advantage of some new features (primarily 9-slice primitives) and so far it's been a pleasant experience to use. I've been experimenting since with migrating from blend to VSCode as our main text editor as we prefer to edit the text directly due to our experience and the majority of said transition has been fairly simple.

However one issue we've noticed in our VSCode is intellisense, with custom variables from codebehinds/viewmodels not autocompleting or even being detected. Which is something blend was able to do and we just wanted to figure out where we've gone wrong/if there's an issue.

The lang server in question seems to be working correctly when VSCode is opened from studio via the context menu for Noesis intellisense in xaml and C# in our codebehinds/.cs files. However when looking to bind to a custom property in our xaml the intellisense doesn't seem to pickup on it/autocomplete the variable name. However typing in the name I can see it's correctly binding to the value as the nifty Xaml Preview loads the correct assets/values when completed.

Currently it will load the newly generated .slnx file which I think is correct and it should therefore be able to detect/sense these custom variables and autocomplete them in the xaml. I think we've got it all done correctly but just want to double check/make sure we're not missing anything obvious.

Many thanks in advance.

Thanks for your feedback!

However one issue we've noticed in our VSCode is intellisense, with custom variables from codebehinds/viewmodels not autocompleting or even being detected. Which is something blend was able to do and we just wanted to figure out where we've gone wrong/if there's an issue.

New controls should autocomplete correctly. For example, in the toolkit package, new classes like GridImage, Gear, etc., as well as your own controls, should autocomplete. Could you please confirm whether this is working correctly?

However when looking to bind to a custom property in our xaml the intellisense doesn't seem to pickup on it/autocomplete the variable name

The design-time DataContext is not implemented in VSCode, so bindings to the DataContext won't autocomplete. I understand this is the problem you're having, right? Binding to other elements on the page should autocomplete correctly.

Currently it will load the newly generated .slnx file which I think is correct

I'm a bit confused here because we don't read any `.slnx` files. The plan is to read the design-time types available in the `.noesis` folder.

Hey jsantos, thanks for the swift response!

I can confirm that new controls such as grid image, ninesliceimage etc. Are all fully auto completing, no issues on that end at all!

Ah that was more what I was concerned about (binding to the datacontext at design time), is there any way to support this via additional tools in VSCode that you know of? Binding to other elements within the xaml e.g. via ElementName and whatnot is fine.

Yeah the .slnx confused me as well, I think this might be a Visual Studio thing potentially as it seems MS are looking to deprecate .sln in favour of .slnx so I think that point can be safely ignored and was more me amalgamating possible issues.

Ah that was more what I was concerned about (binding to the datacontext at design time), is there any way to support this via additional tools in VSCode that you know of? Binding to other elements within the xaml e.g. via ElementName and whatnot is fine.

Support for design-time data context (created in Studio) will be implemented on our side. Please create a ticket if you’d like to track this feature.

Oh I am glad to hear this is coming along at least! I've made a ticket here which I believe is all correct but I haven't needed to do so before so hopefully it's all in order: #5222 I will mark this as solved, thanks again jsantos for the clarification!

Thank you!