I relied on the order of returned methods for caching purposes.
In my case the cache (consisting of a member-index to member lookup) was
created at application startup, and was referred to during application
execution. In 1.1 this worked (because members would be returned in the same
order throughout the application session).
In .Net 2.0 it doesn't work because every time you ask for a list of
members, they come back in a random order. This randomness was added by the
..Net team in 2.0 to ensure you don't rely on the order.
Relying on the order of members between sessions (ie. in serialization)
certainly isn't a good idea, many things can change between sessions. But
*during* the session objects won't be changing! And so they should be
reliable. Their solution to the problem of having people rely on the order
of reflection members being returned doesn't take my scenario into account.
It used to work in 1.1 and doesn't in 2.0 and that makes it a breaking
change.
Heck my applications break what more proof do I need to give! :)
When you say feedback page - do you mean in ladybug? or the feedback page
for the breaking changes list?
Thanks for responding,
John
"Kevin Yu [MSFT]" <v-****@online.mic rosoft.com> wrote in message
news:66******** ******@TK2MSFTN GXA02.phx.gbl.. .
Hi John,
Thanks for your feedback. But I didn't see this in the breaking changes
list. IMO, relying on the order of the returned methods from Reflection is
not reliable.
I suggest you sign in into the feedback page and suggest the product team
to make this breaking change listed. Because in this way, the products
team
will see this immediately.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."