Bug 23684 - Possible Enhancement to WinPhone Forms
Summary: Possible Enhancement to WinPhone Forms
Status: RESOLVED FEATURE
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-10-08 12:04 UTC by Cody Beyer (MSFT)
Modified: 2016-05-28 00:44 UTC (History)
5 users (show)

Tags: ac
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FEATURE

Description Cody Beyer (MSFT) 2014-10-08 12:04:38 UTC
As a URI is used as the key for the cache of an image, there is the risk that a long URI causes an exception, if it is over 260 char. It appears that this happens in Xamarin.Forms.URIImageSource.GerStreamAsyncUnchecked when it stored the files. Perhaps it could create a hash from the URI instead?

Thanks!
Comment 2 Samantha Houts [MSFT] 2016-05-28 00:44:07 UTC
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.

Warm regards,
Xamarin Forms Team