We’re happy to announce that we’re ready for another public RC that includes a whole bunch of bug fixes.
This prerelease contains a number of bug fixes:
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:
Our NuGet package ids are:
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!
was this fixed?
social.msdn.microsoft.com/.../85755525-38c2-4b89-9911-0f457cdf7442
Sorry, only the issues listed in the body of the post are fixed in this release.
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 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?
@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.