Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
There are many instances where we need to use an ImageSource but it doesn't fit the exact pattern defined by the ImageSource class tree.
Case in point: I have a client whose image data is on an FTP server, but ImageSource expects HTTP or file paths.
It's not possible for Xamarin.Forms programmers to think of all possible types of ImageSource and provide code for them. We need an extensible mechanism so we can make our own tools on top of yours.
Thanks for your suggestion. We already thought about this and we might consider this feature for a future release.
With the struggle to manage assets in projects these days (especially cross-platform) it makes sense to think about an SVGImageSource. With subclassable ImageSource I could make my own...
*** Bug 32949 has been marked as a duplicate of this bug. ***
Thank you for taking the time to submit this feature request. We like this idea and have added it to our internal feature tracking system.
Xamarin Forms Team