WCF Data Services 5.0.2-rc Prerelease


We’re happy to announce that we’re ready for another public RC that includes a whole bunch of bug fixes.

What is in the prerelease

This prerelease contains a number of bug fixes:

  • Fixes NuGet packages to have explicit version dependencies
  • Fixes a bug where WCF Data Services client did not send the correct DataServiceVersion header when following a nextlink
  • Fixes a bug where projections involving more than eight columns would fail if the EF Oracle provider was being used
  • Fixes a bug where a DateTimeOffset could not be materialized from a v2 JSON Verbose value
  • Fixes a bug where the message quotas set in the client and server were not being propagated to ODataLib
  • Fixes a bug where WCF Data Services client binaries did not work correctly on Silverlight hosted in Chrome
  • Allows "True" and "False" to be recognized Boolean values in ATOM (note that this is more relaxed than the OData spec, but there were known cases where servers were serializing "True" and "False")
  • Fixes a bug where nullable action parameters were still required to be in the payload
  • Fixes a bug where EdmLib would fail validation for attribute names that are not SimpleIdentifiers
  • Fixes a bug where the FeedAtomMetadata annotation wasn’t being attached to the feed even when EnableAtomMetadataReading was set to true
  • Fixes a race condition in the WCF Data Services server bits when using reflection to get property values
  • Fixes an error message that wasn’t getting localized correctly
Getting the prerelease

The prerelease is only available on NuGet. To install this prerelease NuGet package, you will need to use one of the following commands from the Package Manager Console:

  • Install-Package <PackageId> –Pre –Version 5.0.2-r
  • Update-Package <PackageId> –Pre –Version 5.0.2-r

Our NuGet package ids are:

Call to action

If you have experienced one of the bugs mentioned above, we encourage you to try out the prerelease bits in a preproduction environment. As always, we’d love to hear any feedback you have!

Comments (4)

  1. Matt Meehan says:

    Sorry, only the issues listed in the body of the post are fixed in this release.

  2. Pavel Korsukov says:

    I have found a bug in the prerelease. It seems that DataServiceKey for ID field is hardcoded. What I have done:

    1. Wrote some code from sample http://www.codeproject.com/…/Advanced-using-OData-in-NET-WCF-Data-Services (under header Exposing another Data Model)

    2. Changed ID field name to something another

    [DataServiceKey("Name")]

       public class ProcessModel

       {

           /// <summary>Name of the process.</summary>

           public string Name { get; set; }

           /// <summary>Process ID.</summary>

           public int ID_sample { get; set; }

       }

    3. This is it! Service fails with unexpected error. No error details as always.

    In my project I have rolled back to version 5.0.

    Could you please fix this?

  3. @Pavel: First, see this blog post for information on how to get verbose errors: blogs.msdn.com/…/debugging-ado-net-data-services.aspx. By default, error information is not written out in production code for security reasons.

    The most common reason for problems with [DataServiceKey] is that the classes using it are defined in a seperate assembly which is still referring to an older version of WCF Data Services. Please make sure you update ALL references when upgrading. That said, if you are still having problems, please post something on our forums so we can investigate further.