You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm getting this issue when running UnitTests using Avalonia.Headless(.Xunit).
XamlX.XamlParseException: 'Unable to resolve type Xyz from namespace Abc
The issue is not appearing in normal app setups and can be solved using the workaround described in #7200
( GC.KeepAlive(typeof(TypeInReferencedAssembly)) in App.OnFrameworkInitializationCompleted() )
I guess this is also a similar issue to the solved #7200 thus only appearing in this specific setup.
To Reproduce
Prepare an AssemblyInfo with XmlnsDefinition Attribute for the library you want to test e.g.
using Avalonia.Metadata; [assembly: XmlnsDefinition("https://my.controls.url", "Abc.Namespace")]
Try test it in an Avalonia.Headless testing project for example parsing a Xaml:
Expected behavior
All types beeing resolved. Can be currently reached by modifing the TestApp type like this (line 20):
Thank you for your help
Avalonia version
11.0.10
OS
Windows
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I'm getting this issue when running UnitTests using Avalonia.Headless(.Xunit).
XamlX.XamlParseException: 'Unable to resolve type Xyz from namespace Abc
The issue is not appearing in normal app setups and can be solved using the workaround described in #7200
(
GC.KeepAlive(typeof(TypeInReferencedAssembly))
inApp.OnFrameworkInitializationCompleted()
)I guess this is also a similar issue to the solved #7200 thus only appearing in this specific setup.
To Reproduce
using Avalonia.Metadata;
[assembly: XmlnsDefinition("https://my.controls.url", "Abc.Namespace")]
Expected behavior
All types beeing resolved. Can be currently reached by modifing the TestApp type like this (line 20):
Thank you for your help
Avalonia version
11.0.10
OS
Windows
Additional context
No response
The text was updated successfully, but these errors were encountered: