The goal of the release is to add improved cross platform support.

Beta3: (2016-04-17)

• Fix #90 FormsAuthentication on Desktop Platforms
  • Desktop client now support Cookies by default (which means Forms authentication just works)
  • Can be controlled via WebDomainClientFactory.CookieContainer
• WebDomainClientFactory can now be overridden (bug in beta2)
• Enforce build ordering so we don't get error saying web project did not build which is one of the errors issue #73 Code generation fail for WPF if xaml references local types
  • You will se a new project reference "OpenRiaServices Server Project Link" in projects with the code genereation enabled.
• Automatically generate WebContext for .exe projects
• Use msbuild property OpenRiaGenerateApplicationContext to control webcontext generation instead of just using SilverlightApplication variable
• Fix #91 Difference in validation behaviour between Silverlight and .net
  • Desktop version now uses same validation logic as Silverlight build
• ApplicationServices classes are moved to the Client assembly
  • This means that portable libraries and windows apps can now access them and have AuthenticationServices generated
• All project now compiles
• Appveyour compatibility - all projects now builds successfully on ci.appveyor.com

Beta2: (2016-02-16)

• Fix #89 NullReferenceException in WebDomainClientFactory.CreateDomainClientCore
• Desktop client now requires .Net 4.5, with 4.5.2beeing the lowest supported 4.x version of the .Net runtime the client has been updated to 4.5
• Now Entityt and ComplexObject implements INotifyDataErrorInfo also for the Desktop client

Beta1: (2016-02-07)

DomainClientFactory

The communication layer on the client can now be easily switched, for an example implementation se https://github.com/Daniel-Svensson/OpenRiaPlayground/tree/master/HttpClient

PR: https://openriaservices.codeplex.com/SourceControl/network/forks/danneesset/openriaservices/contribution/8505

What:

• Introduces a new extension point for controlling what kind of DomainClient gets created and how.
• Allow Desktop and Portable clients to specify a "Base uri" so that the default constructor generated by the code gen can work outside silverlight.

This should hopefully remove the last strong dependency from the "core" Client on the current WCF based Client.Web assembly so that it becomes possible to add new service communication
protocols in the future.

Why?

• Make the core assembly independent of how we communicate with the Server.
• Allow new communication protocols in the future such as talking to the DomainController odata service, (soap/json endpoints) etc as well as for providing a portable alternative for the current Client.Web assembly for talking with normal DomainServices.

How to use it:

• Most user don't do anything at all, it will setup a DomainClientFactory automatically
• For "advanced" scenarios the user can set DomainClient.DomainServiceFactory to a WebDomainClientFactory instance.

Ex: One can add the following code att application startup (ex: App ctor) before WebContext or any other DomainContext get created

```
DomainContext.DomainClientFactory = new WebDomainClientFactory()
{
ServerBaseUri = new Uri("http://localhost:51359/ClientBin/", UriKind.Absolute),
};
```

For another example with both Silverlight, WPF and Windows 8 app see https://github.com/Daniel-Svensson/OpenRiaPlayground/tree/master/HttpClient (WIn8 upp is not updater to beta1)