Advanced Forum Search Results
-
What behavior do you actually see? Do you see default splash screen instead of your custom XAML?
First of all make sure that SplashScreenSource can be found, it should be located alongside your HTML page (splash screen URI is relative to the host HTML page, not to the XAP file location). If it is still not shown, check that your XAML is ...
-
Hi,
Actually we are already considering this idea for future versions of Silverlight. Right now we are in the early stages of planning next version, so at this point we cannot give any details or promise anything. But keep your feedback coming, it's certainly useful for us. Thanks!
-
What is the initial value of image.source? is it a valid URI?
Error 4001 means the image cannot be found or cannot be loaded for some reason (wrong format, corrupt file, etc). Most likely the initial value of the property you are binding to is empty string. When you add the image element to visual tree, it tries to load its source and ...
-
Try ImageControl1.Source = new BitmapImage(new Uri("newimage.png", UriKind.Relative));
BitmapImage is defined in System.Windows.Imaging.
-
First of all, I suppose you already updated your AppManifest.xaml to use ExternalCallersFromCrossDomain="ScriptableOnly" instead of FullAccess, right? There was one more breaking change for cross-domain apps: MIME type for XAP files is now required to be application/x-silverlight-app. Can you check that your web-server sets the ...
-
I think this has been recently fixed. I've been able to repro on RC0 bits, but latest internal post-RC0 bits do not crash on this anymore. But thanks for reporting this anyway!
-
Thanks for reporting this! I will bring this to developers attention. Unfortunately I cannot suggest any workaround at the moment.
-
Well, as far as I understand that's not a bug in Silverlight, that's a problem with your application. When you add an Image element with incorrect source to a visual tree, you are getting AG_E_NETWORK_ERROR and this is by-design. It's up to you how to work around this situation best, as this depends on what is easier for you and what ...
-
You are right, these methods are not overridable anymore. This change was made to make typeconverter implementation compatible with WPF (WPF also doesn't allow overriding these methods). I will contact breaking changes doc author and make sure this is documented.
Thanks for reporting this!
-
That's because this element already belongs to another visual tree. I agree, error message is very confusing, we have a bug for this. But still you cannot have single UIElement belonging to multiple trees, so your design is incorrect. You could try removing this element from the canvas before adding it to another tree - this might work (I ...