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
GitHub or Developer Community 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.
public ObservableCollection(List<T> list)
has an incorrect implementation: it only passes the source list to its base (which is Collection<>).
As read in the DotNet documentation, and tested in reality, this constructor should create a new list and duplicate the items (one by one) of the source list.
The practical difference is that in the current Mono implementation we have only one list with two references, but in DotNet we have two different lists.
So a program based on this wrong assumption can work fine in Mono but not in dotnet.
That provoked a bug in my program, for example.
See here for more info: http://msdn.microsoft.com/en-us/library/ms653202
"The elements are *copied* onto the ObservableCollection(Of T) in the same order they are read by the enumerator of the list."
Fixed in master