Sorry for the late reply! Thanks for taking a look at this issue.

It seems like the errors only appear when VSCode is open.

I am trying to reference an image like usual: <BitmapImage x:Key="Images.Borders.Base" UriSource="/Assets/Project/Features/Game/Features/Combat/Core/Media/T_Background.jpg" /> The image appears under the XAML dependencies correctly, and it shows when the game is played in Unity, ...

Just to be clear, this happens in the editor. I can change a single line of code and it then gives me this error until I reimport. Yes, I've never had to reference anything manually. I have a Root UserControl which handles scaling and a NavFrame UserControl inside of that which you push elements int...

I don't know if this is possible because all of my usercontrols are used with my navigation system. I load XAML files using Addressables and then push them onto the stack. Because of this, none of the controls reference each other in the editor. Is this a new limitation? I never had this issue in th...

I only have two XAML files in my project now, but every time Unity complies and the Xaml is used I get "Xaml not found '...'". To fix this, I have to change reimport each xaml file. They then work again until Unity recompiles again. This happens in a blank Xaml file: using Noesis; namespac...

When I create a new project, I create my own ResourceDictionary to set as the Application Settings. However, this replaces the Noesis style. To overcome this, I usually just copy the styles into my assets folder and reference them like this: <ResourceDictionary.MergedDictionaries> <ResourceDictionar...

When you create a BitmapImage in a ResourceDictionary, you have to use a string to set the path of the resource: <BitmapImage x:Key="Image.Icon.xxx" UriSource="xxx.png"/> This can easily break if you move around the assets in your project. A better way would be to declare the Bit...

It seems to me this just creates a large barrier to try Noesis in any real fashion as 10 minutes is extremely short to work with. How can you justify someone needing paying $195 to even try developing with Noesis, which is simply a UI framework, when entire game engines are completely free to start ...

If I understand these changes correctly, you can't use Noesis for more than 10 minutes at a time without buying a license -- even if you hadn't yet released your project? Isn't this a really bad change? I would expect you to need a license for when you are about to release your project on a storefro...