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
So I get Squiggly Lines under "<UserControl ", and following Exception.
UriFormatException: Ungültiger URI: Das URI-Format konnte nicht bestimmt werden.
UriFormatException: Invalid URI: The URI-Format could not be determined. <-Manual translation
StackTrace:
bei System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
bei System.Uri..ctor(String uriString)
bei CachedImage.Image.<ImageUrlPropertyChanged>d__0.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
bei System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
I had a Workaround for the other ImageCache-Controls, where I can´t use the XAML-Designer except I Remove the ImageUrl-Property from the Control temporarily.
This is somehow strange to me.
How does the ImageCache can "Bleed" into a UserControl?
thx in advance Zui
The text was updated successfully, but these errors were encountered:
Hello.
I have in Visual Studio 2019 the issue of an UriFormatException.
I created a new UserControl as a View. Moved to a Namespace "Views".
But I don´t have Anything placed in the UserControl yet.
No ImageCache References or a ImageCache-Control.
So I get Squiggly Lines under "<UserControl ", and following Exception.
I had a Workaround for the other ImageCache-Controls, where I can´t use the XAML-Designer except I Remove the ImageUrl-Property from the Control temporarily.
This is somehow strange to me.
How does the ImageCache can "Bleed" into a UserControl?
thx in advance Zui
The text was updated successfully, but these errors were encountered: