Field not found: System.Collections.Generic.KeyValuePair 2.Value

6 Oct 2005 10:25 PM

dotdevelop@gmail.com

We have recently upgraded from VS.NET 2005 Beta 2 to VS.NET 2005
Release Candidate on all our development machines. It appears it the
Framework is upgraded from v2.0.50215 to v2.0.50727. This appears to be
a major change. For any of our 2.0 projects that use collections, I am
getting missing field exceptions, i.e. "Field not found:
System.Collections.Generic.KeyValuePair '2.Value'". I dont want to
regret this upgrade and am really hoping to find an answer here. Any
help or insight would be greatly appreciated.

6 Oct 2005 10:38 PM

Jon Skeet [C# MVP]

dotdeve***@gmail.com <dotdeve***@gmail.com> wrote:

> We have recently upgraded from VS.NET 2005 Beta 2 to VS.NET 2005
> Release Candidate on all our development machines. It appears it the
> Framework is upgraded from v2.0.50215 to v2.0.50727. This appears to be
> a major change. For any of our 2.0 projects that use collections, I am
> getting missing field exceptions, i.e. "Field not found:
> System.Collections.Generic.KeyValuePair '2.Value'". I dont want to
> regret this upgrade and am really hoping to find an answer here. Any
> help or insight would be greatly appreciated.

According to msdn2.microsoft.com, it's not a property rather than a
field.

Things are bound to change between betas, release candidates, and
released products. I think it's highly unlikely that the properties
will change back to fields, so you'd have to make the change sooner or
later anyway.

If you don't like having to make this kind of change, it's a bad idea
to be using betas in the first place.

--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too