Hi,

I am developing using Noesis Studio and by coding XAML. I am using the Visual Studio extension for coding XAML NoesisGUI XAML Tools but when I open the XAML file of a page or components, the extension gives me:
"Unkown element type 'Component'".

While the NoesisGUI XAML Tools extension says "Unkown element type 'Component", the Noesis Studio isn't showing any errors.

Also, when I fix something on the XAML code, the extension doesn't update in real time and it keeps showing the same messages even tho I have fixed the code. I have to restart Visual Studio every time.

I also tried to open a page of your Sample "Ombra", and it gives me the same message on Visual Studio "Unkown element type 'Component".

Is that normal?

Hi Lollo,

When running VSCode independently, this is expected as Components are a Noesis Studio-exclusive experimental feature that is not yet supported in the NoesisGUI runtime, and therefore isn't recognised in the VSCode Extension when unpaired from Studio.

However, if you have VSCode running alongside an open instance of Studio, VSCode will hook into Studio's XAML parser in which they are recognised, and the errors will disappear.

In any case, in the context of the included Samples, you can safely ignore any Component errors, as they don't adversely affect Project functionality within Noesis Studio.

With that said, Components not being supported in the runtime is something that should be kept in mind if you are developing your own Projects with the intention of usage outside of Studio. Instead, at the time being, we would recommend using DataTemplates to fulfill the majority of the functionality that Components provide.

Let us know if you have any other questions,

- Dorian

Please also note that our VS Code extension can connect to custom language servers. You can create your own server, and Studio provides its own. If you have VS Code open while Studio is running, our extension will connect to Studio (you can see this in the lower-right corner of VS Code). All Studio extensions, such as components, should then be properly highlighted.

Thank you for your replies and for specifying that I must use DataTemplates instead of Components for NoesisGUI runtime.

However I am still confused because when Noesis show some errors, and I click "Show errors in VSCode", the NoesisGUI XAML Tools isn't showing any errors. I am a little bit confused and I think that anyway NoesisGUI XAML Tools extension and Noesis Studio should be "synced". Am I using it wrong?

Do you have any ETA on when this will happen?

Thank you

Hi Lollo,

I edited my initial response to you to clarify this a bit more, but essentially, yes, your intuition is correct about the 'sync' between Studio and VSCode.

If you open VSCode on its own, it uses the 3.2.10 Noesis XAML parser (that doesn't include Components), and these errors will be display.

If you open VSCode with an instance of Studio running on your machine, VSCode will hook into Studio's XAML parser (that includes Components), and these errors won't display.

As as an immediate resolution, all you really need to do to be error-free is just to have an instance of Studio running whilst you're working in VSCode. Even just having the launcher open without necessarily opening a Project will achieve this.

- Dorian

However I am still confused because when Noesis show some errors, and I click "Show errors in VSCode", the NoesisGUI XAML Tools isn't showing any errors. I am a little bit confused and I think that anyway NoesisGUI XAML Tools extension and Noesis Studio should be "synced". Am I using it wrong?

They are synced (if you follow Dorian’s instructions and have Studio open), but there are a few cases where you may see an error in Studio that doesn’t appear in VS Code. We consider this a minor issue and are working on it, but if you’d like to file a ticket (including your XAML), please feel free to do so.

Thanks for your help.