AspNetCore - 1.3.1

New Http status codes returned
- Submit can now return 409 and 422 Unprocessable Entity (for conflicts and validation failure)
- Use 415 unsupported media type instead of 400 for unsupported content type

5.6.0 / AspNetCore 1.3.0

AspNetCore 1.3.0 (#518)

New Http status codes returned
- 401 unauthorized, 403 forbidden and 422 Unprocessable Entity (for validation failure)
- IMPORTANT: POSSIBLE BREAKING CHANGE: this will not work with the obsolete wcf based domain client
New Methods on IServiceCollection for Setup and registration of DomainServices
- AddOpenRiaServices now accept a callback for configuring Options
  - AddOpenRiaServices(Action<OpenRiaServicesOptions> configure)
- New helper methods for registering DomainServices
  - AddDomainService<TDomainService>()
  - AddDomainService(typeof(DomainService))
  - AddDomainServices(params IEnumerable<Assembly>)
Simplified MapOpenRiaServices
- Add AddRegisteredDomainServices() to "map" (add endpoints) for all registered domain services
- Added new overloads of MapOpenRiaServices() which do not require a callback, it will map app registered domain services
- MapOpenRiaServices now throws if there are no domain services registered
Added new OpenRiaServicesOptions for configuration openria services
- Se Readme for a description of the settings
The StatusCodes property on exception will now be 403 when authorization fails but the user is logged in as an authenticated user (it was 401 before)
Add more nullability annotations to AspNetCore hosting

5.6.0

This is proably the last version with for WCF based hosting

BREAKING CHANGES:

Drops support for .NET6 and .netstandard2.0
Stop shipping WCF based domainclient as part of OpenRiaServices.Client.Core nuget The WebDomainClient has been depreciated since 2023
- code gen
NOTE: WCF based hosting is considered depreciated and will be removed in the near future

Client Improvements

Handle exceptions when Exception StatusCode is 403 (Required for AspNetCore 1.3.0)
Set Accept header to "application/msbin1" (#521) for BinarHttpDomainClient
Client nugets no longer have a dependency on System.ServiceModel

General Improvements

Update nuget package dependencies
Update to latest version of Mono.Cecil
Updated integration test to run on .NET 8 instead of .NET Framework
Updated E2E integration tests no longer use WCF based client

5.5.0 / EF Core 3.1.0 / AspNetCore 1.2.0

EF Core 3.1.0

Initial support for Owned Entities for one-to-one navigation properties (#500)
- Owned entities without explicit keys are mapped to OpenRiaServices's [Complex Types]
- Owned entities with explicit keys are generated as normal "Entities" but are automatically annotated with [Composition]
- EFCore "Complex Types" introduced in EFCore 8.0 does not have any special handling
Add new helper method AttachAsModified<TEntity>(TEntity entity) (#506)
- It works similar to the existing AttachAsModified extension methods on DbSet but
  - is smarter (works with and without original entity)
  - reduces code that needs to be written and works both with and without "OriginalEntity" (RoundTripAttribute)
Add package README to OpenRiaServices.Server.EntityFrameworkCore

AspNetCore 1.2.0

Add support for specifying endpoints routes (#508, issue: #507) You can choose between 3 different approaches to how the endpoint routes are generated. See AspNetCore readme for more details.
- WCF will generate the same routes as WCF RIA Services Some-Namespace-TypeName.svc/binary/Method
- FullName will generate routes with the full name of the DomainService Some-Namespace-TypeName/Method
- Name will generate routes with the short name of the DomainService TypeName/Method

Code generation

Log whole Exceptions in DomainServiceCatalog instead of just message (#502), for better error messages on code generation failure
Call "dotnet CodeGenTask.dll" instead of "CodeGenTask.exe" #503
Support for the 3 different approaches to how the endpoint routes are generated for AspNetCore hosting (#508)
Replace obsolete AssociationAttribute with new EntityAssociationAttribute on client (#509)

Client

Replace obsolete AssociationAttribute with new EntityAssociationAttribute on client (#509)
- The client currently detect AssociationAttribute but it will be removed in future versions.
- Ensure you have the corresponding version of the Code generation

Client

AspNetCore 1.2.0

EF Core 3.0.0

Target EF Core 8
- IMPORTANT EF Core 8 is NOT backwards compatible with models (DbContexct) classes compiled against earlier versions of EF Core. Methods such as HasName in OnConfigure will throw MethodNotFoundException This means that to use EF Core 8 all referenced EF Core projects needs to be updated to 8.0
Drop support for earlier TargetFrameworks
- Due to limitations above with binary breaking changes in EF Core earlier frameworks will not be supported to reduce risk of mixing EF Core versions.
- Use the 2.0.* version of the nuget package if you need support for earlier versions of EF COre

5.4.3

Server

Reduced allocatgions when parsing queries on server (both WCF and AspNetCore hosting) in #485
Update nuget dependencies and add new dependencies to OpenRiaServices.Hosting.Wcf
- System.Collections.Immutable and System.Memory are new dependencies of Wcf hosting
.NET Framework builds now includes the smaller portable pdb's instead of of the old "full" windows style pdb's
- NOTE: For .NET Framework apps ensure that supportedRuntime in app.config and corresponding setting in web.config does not specify an older runtime if you wan't line numbers in stack traces.

5.4.2 / AspNetCore 1.0.0

.NET8

Build with .NET8 sdk and run AspNetCore tests with .NET8 by @Daniel-Svensson in #463
Run most client, server and code generation tests with .NET8 by @SandstromErik in #458

Code generation

Do not use attributes reserved for the compiler in code generation. Will make it possible to use nullable reference types and the required modifier for fields and properties by @SandstromErik in #472

AspNetCore updates

Various updates by @Daniel-Svensson in #466
- Add authentication documentation
- Use FrozenSet in first location (QueryStringConverter)
- Update versionprefix to 1.0.0 (for next release)

Testhost

Add support in DomainServiceTestHost for asynchronous queries that return a single entity by @erikoijwall in #464

Other

Build improvments, including set MSBUILDDEBUGPATH allowing troubleshooting of build failures by @Daniel-Svensson in #463
Update nuget dependencies for tests by @Daniel-Svensson in #468
Fix test which would sometimes hang by @Daniel-Svensson in #469
Add tests to see that codegen works with nullable reference types by @Daniel-Svensson in #470
Use BinaryHttpDomainClient in AspNetCore Test by @SandstromErik in #471

5.4.1

Code generation

Fix .NET7+ code generation crash for RegularExpressionAttribute #449

Client

Improved performance of property setters (and Add) #451 #453 #456
- Use Dictionary.TryAdd for minor perf improvements in entityset add by @Daniel-Svensson in #451
- Speed up ValidateProperty by @Daniel-Svensson in #453
- Improve perf of ReplaceErrors by @Daniel-Svensson in #456

Other

Remove typo by @omimakhare in #446
Use mstestv3 as testing framework by @Daniel-Svensson in #372
Move more tests from EndToEnd tests to Client.Test by @Daniel-Svensson in #454
Add new test that validate how object level validation interact with property level validation by @Daniel-Svensson in #455
Various fixes by @Daniel-Svensson in #460

5.4.0

This release fully supports .NET 6+ for both server and client without having to rely on workarounds to have the code generation work.

Code Generation Supports NET6+

Support net6+ on server (#414)
- Add version of code generation which allows server project to be .NET 6 or later
- Works with dotnet build - you can build without installing Visual Studio

Client

Ensure exceptions from xxxOperation callbacks and unhandled exceptions are rethrow on the SyncronizationContext. (#424)
- This allows events such as DispatcherUnhandledException (for WPF) to be used for showing error messages immediately
Add net6.0-windows TargetFramework for client (#436)
- EntitySet and EntityCollection now implements ICollectionViewFactory for net6.0-windows. improving supprot with controls using CollectionView
- This change came in WCF Ria Services SP1 WCF Ria Services SP1
  
  DataForm Add/Remove for EntitySet and EntityCollection With our initial V1.0 release, many of you found that a DataForm bound to an EntitySet or an EntityCollection did not support the Add or Remove buttons. This was a difficult cut to make in V1.0, so I’m pleased to announce that with V1.0 SP1, this is now supported. Silverlight 4 introduced the ICollectionViewFactory interface, with support integrated into DataGrid and DataForm, and both EntitySet and EntityCollection now implement that interface to allow the Add/Remove features to light up.
The WCF based WebDomainClientFactory will not receive any new changes and is now marked as obsolete. It is recommeded to switch to OpenRiaServices.Client.DomainClients.BinaryHttpDomainClientFactory instead.

Other

Run E2E tests against AspNetCore hosting
Various smaller performance fixes and code cleanup (#438), #435

AspNetCore 0.4.0

AspNetCore
- Copies "All" attributes to endpoint metadata
  - Some attributes sucha as Validation, Authorization and other attributes specific to OpenRiaServices are not copied
- AddDomainService() methods inside MapOpenRiaServices now returns IEndpointConventionBuilder allowing conventions to be specified per DomainService
```
app.MapOpenRiaServices(builder =>
{
    builder.AddDomainService<Cities.CityDomainService>()
        .WithGroupName("Cities");
});
```
- Updated README.md and added Sample project
- Make it compatible with more middleware such as OutputCache middleware by "Completing" responses
- CHANGES:
  - services.AddOpenRiaServices<T>() now requires T to derive from DomainServce
  - services.AddOpenRiaServices<T>() has different return type

5.3.1 with EFCore 2.0.2 and AspNetCore 0.3.0

Code Generation
- Switch to using Mono.Cecil to parse pdb files during code generation (#410) This should make it possible to use portable and embedded pdb's on the server
AspNetCore
- New extension method to add OpenRiaServices to services from #413 by @ehsangfl.
```
services.AddOpenRiaServices<T>()
```
- New extension method to add OpenRiaServices to pipeline from #413 by @ehsangfl.
```
endpoints.MapOpenRiaServices(opt => opt.AddDomainService<T>())
```
- Add Net7 build target to support "Finally Conventions" (IEndpointConventionBuilder.Finally)
- Add OpenRiaServices.Server.DomainOperationEntry to endpoint metadata
  - This allows end user to easier implement additional conventions (such as Open Api or similar)
- Copy AuthorizationAttributes to endpoint metadata for queries and invokes to support AspNetCore Authorization
  - Attributes can be set on either method or class level
- Fixed serialization of sizes larger than 1 GB

Other

Updated nuget packages

5.3.0 with EFCore 2.0.1

Fix shadow property issue in EF Core DB Context extensions (#397):
- Based on Allianz PR #393
- Fix bug with shadowproperties being marked as modified when performing AttachAsModified in DbContextEFCoreExtensions
DomainServiceTestHost improvements 1 (#395):
- Allow usage of CRUD-methods ending with Async in testhost.
DomainServiceTestHost improvements 2 (#396):
- Add support for async IEnumerable queries in test host, i.e. querys returning async Task<IEnumerable<

Other

Fixed github Code QL validation of builds
Updated nuget packages

5.2.0

Client: Make construktors for Operation classes public to make them more testable (#387)
- Add new public constructors to LoadOperation, InvokeOperation and SubmitOperation
DomainServiceTestHost improvements (#386):
- Add constructor which accept a single user (IPrincipal)
- BREAKING CHANGE: Constructor taking in Func<> and user does no longer accept null "user"
  - use constructor without user in order to use the "default" user
  - pass in an "unauthenticated" user to use an "unauthenticated" user
Remove WCF Depdendency from tooling (#377)

Other

Updated nuget packages used in tests (#382)

EFCore 2.0.0

Support for EF Core 6.0 (#385) - by @lindellhugo with help from @ehsangfls code
- Added support for EF Core 6.0 (requires net 6.0)
- Added support for new EF Core attributes ValueGenerated.OnUpdate and ValueGenerated.OnUpdateSometimes (only EF Core 6)

AspNetCore 0.2.0

Fix data corruption bug in 0.1.2 for large requests (#379)
- Prevent problem where output buffer becomes incorrect when parsing large requests from the client on x86 systems.
Improved handling of operation cancelled exceptions (#381) by @SandstromErik
- Swallow or return completed task instead of throwing OperationCanceledExceptions

5.1.1

Add net 6.0 as target framework for OpenRiaServices.Server.UnitTesting (#364, #371)
HttpDomainClient: Buffer requests så HTTP header content-length is set #370

AspNetCore 0.1.1

AspNetCore: Use route order 0 instead of 1 (#357)
AspNetCore: Prevention for DOS attacks where attacker specify large content-length #373

5.1.0

Overview / Major features

Support for NET 6
- AspNetCore based hosting via OpenRiaServices.Hosting.AspNetCore #346
  - See Readme.md and TODO.md for usage details and more details about what works.
- Packages such as OpenRiaServices.Server and OpenRiaServices.EntityFramework are now compiled against net6.0 as well
Support for EntityFrameworkCore via OpenRiaServices.Server.EntityFrameworkCore
- Se #323 for more details (PR #351, #335)
New BinaryHttpDomainClientFactory which is a HttpClient based transport on client (without WCF dependency) which works with Blazor (With sample in samples directory).

DomainContext.DomainClientFactory = new OpenRiaServices.Client.DomainClients.BinaryHttpDomainClientFactory(....)
{
    ServerBaseUri = "https://YOUR_SERVER_URI"
};

Server Dependency Injection support
- Allow injecting services to parameters using attribute InjectParametersAttribute
- ValidationContext And AuthorizationContext will also be able to resolve services using GetService(Type) from the configured IServiceProvider
- Add a new IServiceProvider setting to allow resolving services via Microsoft DI #340 when using WCF Hosting

// Setup DI
var serviceCollection = new ServiceCollection();
serviceCollection.AddDomainServices(ServiceLifetime.Transient);
var serviceProvider = serviceCollection.BuildServiceProvider();

// Setup OpenRiaServices to use container
var config = OpenRiaServices.Hosting.Wcf.Configuration.Internal.DomainServiceHostingConfiguration.Current;
config.ServiceProvider = serviceProvider;

What's new since 5.1.0-preview5

NEW: Package OpenRiaServices.Hosting.AspNetCore, OpenRiaServices.Server.EntityFrameworkCore
Fix bug #348 System.IndexOutOfRangeException when domain query is executed which can happen if invoking methods concurrently on DomainClient
DbDomainService now has a constructor which takes a DbContext in order to support Dependency Injection
DbDomainService will no longer create a separate DbContext to resolve conflicts (if the method to create DbContext was overridden and returned a fixed instance it could lead to problems with incorrect conflict detection)

Infreastructure

Allow C# 10 #354
Support for VS 2022
Improve Tooling support for projects targeting multiple TargetFrameworks #352
- This fix ensures that sdk style implicit included code files are detected for server projects targeting multiple target frameworks.

5.1.0-preview5

Make it possible to cache invoke operations #332
- Introduce caching for invoke operations by refactoring and using the same logic as for querys
Allow method (parameter) injection #339
- Allow parameters of type CancellationToken for all kinds of service methods
- Make the generated method return ValueTask so that the UnwrapTaskResult logic from ReflectionDomainServiceDescriptionProvider can be removed (and better performance)
- Allow injecting services to parameters using attribute InjectParametersAttribute

Add a new IServiceProvider setting to allow resolving services via Microsoft DI #340

See example usage in Global Init/Statup below:

// Setup DI
var serviceCollection = new ServiceCollection();
serviceCollection.AddDomainServices(ServiceLifetime.Transient);
var serviceProvider = serviceCollection.BuildServiceProvider();

// Setup OpenRiaServices to use container
var config = OpenRiaServices.Hosting.Wcf.Configuration.Internal.DomainServiceHostingConfiguration.Current;
config.ServiceProvider = serviceProvider;

5.1.0-preview4

BinaryHttpDomainClientFactory improvements and bug fixes
- Serialize parameters based on contact's parameterType in methods without sideeffects #322

5.1.0-preview3

Fix bug in 5.1.0-preview2 where server project had wrong assembly name (#320, #321)

5.1.0-preview2

BinaryHttpDomainClientFactory improvements and bug fixes
- Serialize parameters based on contact's parameterType #318
  
  This fixes a number of potential issues, such as passing "non-serialisable" enumerables such as result of LINQ Select as method parameters
- Properly handle nullable parameters for EntityActions #311
- Make fault handling more tolerant to different variants of Faults #310
Add .netstandard 2.0 build of server project #314 This is intended to unblock development of newer code generation and hosting layers on .Net 6

New code to create BinaryHttpDomainClientFactory

DomainContext.DomainClientFactory = new OpenRiaServices.Client.DomainClients.BinaryHttpDomainClientFactory(new Uri("https://YOUR_SERVER_URI"), () => createHttpClient());

5.1.0-preview1

New HttpClient based DomainClient - BinaryHttpDomainClientFactory (#290)
BREAKING CHANGE Changes to wire format in order to fix serialization of DateTime (nullable and on complex objects) (#289, #75)
- 5.1 Clients need a 5.1 Server
- Server is backwards compatible so that it can be upgraded safly first
Potential BREAKING change: Complex Objects/Typs (classes/structs which are not entities) parameters will now always be validated (#303,
- Previously they were only validated when calling entity actions and not Invoke methods

BinaryHttpDomainClientFactory

Add a new cross platform (Including Blazor wasm) more easily extensible DomainClient for the binary protocol.

Enable binary endpoint to be use on other clients than .Net Framework
Adds support for blazor wasm where the wcf soap based client has problems
Enable easier extensibility such as oath, client side caching, compression etc using standard HttpClient middleware (HttpMessageHandler)
Can support HTTP2 and other more advanced networking features

HttpMessageHandler httpMessageHandler = new HttpClientHandler() { ... };
DomainContext.DomainClientFactory = new OpenRiaServices.Client.DomainClients.BinaryHttpDomainClientFactory(httpMessageHandler)
            {
                ServerBaseUri = "https://YOUR_SERVER_URI"
            };

Or if you want to use factory for your HttpClients you can pass in a function as callback

DomainContext.DomainClientFactory = new OpenRiaServices.Client.DomainClients.BinaryHttpDomainClientFactory(() => createHttpClient())
            {
                ServerBaseUri = "https://YOUR_SERVER_URI"
            };

5.0.1

IMPORTANT: Fix a potential security vulnerability where entity parameters are not validated when calling invoke methods (#292)
- The issue occurs if there are nothing else to validate so if there were validation attributes on the method, any parameters or it contained any "complex objects" then validation happened as expected. Thanks to @ehsangfl for finding and helping to find the cause of the issue
Allow nullable parameters to GET methods to be sent using same format as non-nullable parameters This enables the "HttpClient" based sample DomainClient for Xamarin etc. to work, and prepares for the upcoming official version (#290)
Make it clear that DomainClientFactory must be set at startup (#301) Throws exception instead of trying to create a instance which does not work

Update dependencies

Mono.Cecil 0.11.3 -> 0.11.4
System.ServiceModel.Http 4.8.0 -> 4.8.1

Infrastructure

Target C# 9.0 when compiling

5.0

Overview

Server is now asynronous which allows it to handles burst in load much better and generally better performance (latency/CPU/memory) under load.
Client networking API the DomainClient is now based on Task instead of using the APM pattern with Begin/End methods
Supported TargetFrameworks has changed
Code generation now works against netstandard 2.0 and netcore 2.1+ clients
Major namespace changes
1. DomainServices is dropped from namespaces and assemblies
2. ApplicationServices has been renamed to Authentication
3. Hosting assembly has been moved to Hosting.Wcf namesapce and moved to a separate nuget package
AspNetMembership authentication (AuthenticationBase and related classes) are moved to a new namespace and nuget package
- Add a reference to OpenRIAServices.Server.Authenication.AspNetMembership if you use it
Full support for IValidatableObject validation (earlier versions only validated IValidatableObject if ValidationAttribute also was specified)

Upgrade instructions

Update both all client anor/or server nuget packages to the new version, dont't mix with v4 in the same project.
Search and Replace OpenRiaServices.DomainServices with OpenRiaServices in all files
Search and Replace .ApplicationServices with .Authentication in all files.
- OpenRiaServices.Client.ApplicationServices has been renamed to OpenRiaServices.Client.Authentication
- OpenRiaServices.Server.ApplicationServices has been renamed to OpenRiaServices.Server.Authentication
If you have been using AuthenticationBase or other classes in the OpenRiaServices.Server.ApplicationServices namespace in your server project
1. Add the OpenRiaServices.Server.Authentication.AspNetMembership nuget package to it
2. Replace OpenRiaServices.Server.ApplicationServices with OpenRiaServices.Server.Authentication
3. Add using OpenRiaServices.Server.Authentication.AspNetMembership; in file which uses AuthenicationBase, UserBase or related classes.
If you have compilation problems in your DomainServices because it overrides methods which do not exist then try to overridde the method with the same name but with "Async" as postfix, method signatures will be different. Eg. replace override of Invoke with override of InvokeAsync.
Fix any additional compilation errors, use changes below for guidance about replacements.
If you are using OpenRiaServices.EntityFramework the framework will now only call the SaveChangesAsync and not SaveChanges so if you are overriding SaveChanges make sure you do the same for SaveChangesAsync
OpenRiaServices.Hosting has been moved to a separate nuget package OpenRiaServices.Hosting.Wcf #251
1. You must add a reference to OpenRiaServices.Hosting.Wcf nuget in your web application
2. Search and Replace OpenRiaServices.Hosting with OpenRiaServices.Hosting.Wcf
Update your web.config file so that it matches the new format Failure to do this step will result in the server not responding to client request If you use packages.config for nuget packages, this step should have been performed automatically.
1. Search for "DomainServicesSection" and change type to "OpenRiaServices.Hosting.Wcf.Configuration.DomainServicesSection, OpenRiaServices.Hosting.Wcf, Version=5.0.0.0, Culture=neutral, PublicKeyToken=2e0b7ccb1ae5b4c8"
2. Replace all other places with OpenRiaServices.Hosting to OpenRiaServices.Hosting.Wcf(if not already replaced)
3. If you reference OpenRiaServices.Hosting with fully qualified assmebly name including version number, the version number must be updated from 4 to 5
Start with building your web project, and only build the client once the server (web project) compiles fine

For better scalability (can be done afterwards):

Update your Query and Invoke methods so that they use async/await where relevant. E.g if you are using EF6, other ORM frameworks or do network or file access.

Samples

A "new" samples repository is availible at https://github.com/OpenRIAServices/Samples

It is currently quite empty but already demonstrates some of the following scenarios:

A simple WFP app on .Net framework
- Includes a number of queries/invokes for manually testing Task returning methods, GET/POST and exception handling
A WFP app on .Net Core
- .net core and netstandard support
- Using Asp.Net Identity for authentication
- Writing your own custom Authentication logic
- Running OpenRiaServices in same project as Asp.Net MVC

5.0.0 RC1

"DomainServices" dropped from all namespaces, filenames as well as nugets and DLLs. #234
- IMPORTANT Search and Replace OpenRiaServices.DomainServices with OpenRiaServices in all files when uprading
Namespace OpenRiaServices.Client.ApplicationServices has been replaced with OpenRiaServices.Client.Authentication search and replace is needed on upgrading #248
OpenRiaServices.Hosting has been moved to a separate nuget OpenRiaServices.Hosting.Wcf #251
- IMPORTANT You must add a reference to OpenRiaServices.Hosting.Wcf nuget in your web application
- IMPORTANT Search and Replace OpenRiaServices.Hosting with OpenRiaServices.Hosting.Wcf in all files when uprading
Updated required version of .Net Framework to 4.7.2 (#241)
Updated dependencies including EntityFramework to latests availible versions #240

Client

IgnoreDataMemberAttribute can now be used on the client to prevent client properties from beeing included/overwritten when loading data using MergeIntoCurrent or the state manipulating methods ApplyState, ExtractState etc. #249
- MergeAttribute which has a similar usage area has been moved to OpenRiaServices.Client.Internal and might be removed in future releases.

Code Generation

Suppress generation of DebuggerStepThroughAttribute from async methods
New handling of shared files #229 Instead of copying all ".shared" files to the Generated_Code folder the server version is referenced instead
- This should build faster builds and allows find all references, refactoring etc to work for shared files
- It is possible to opt out of the new behaviour by adding <OpenRiaSharedFilesMode>Copy</OpenRiaSharedFilesMode> in the project file
- The tooling is updated with a new option
Load Mono.Cecil exclicitly in code generation #255 to fix issue such as #247 without having to do a workaround

Server

Create, Update and Delete methods on server can now return Task #226
The CancellationToken passed to SubmitAsync and InvokeAsync now supports cancellation on client disconnect #250
Security: Don't include stack traces for errors by default #256
Dont use HTTP status code "200 OK" for exceptions (will use 500 Internal Server Error by default) #257
- It is free for library consumers to change the handling of returned HTTP response codes status such as using a "SilverlightFaultBehavior" or similar

Unit Testing

DomainServiceTestHost has received an number of new methods and overloads to help with unit testing async code. (#245)
- Added async methods for DomainServiceTestHost
  - UpdateAsync
  - InsertAsync
  - InvokeAsync
  - QueryAsync
  - SubmitAsync
- Added overloads to Invoke for methods returning Task to fix the following issues
  - Fixed bug when TResult was a Task and returned null (could await null)
  - Fixed bug when TResult was a Task and returned Task

5.0.0 Preview 3

Client

Complete Load/Invoke/Submit and Authentication operations on the ´SynchronizationContext` of the caller instead of saving the SynchronizationContext (#211, #209 for submit, #216, #212)
- This is a behavioral change which might break applications. This means that operations should be started on the UI thread if any data of the DomainContext or returned Operaitons are bound to the UI before completion.
Base SubmitChanges on SubmitChangesAsync (#209)
- Submit operation will now cancel only if the web request is cancelled (and then after cancellation) Update cancellation behavior to be the same as for Load and Invoke (Follow up on #203 and #162)
- Changed extension point for SubmitChangesAsync to a new method called by both SubmitChanges and SubmitChangesAsync protected virtual Task<SubmitResult> SubmitChangesAsync(EntityChangeSet changeSet, CancellationToken cancellationToken)
- Changed extension point for InvokeOperationAsync to a new protected method.
Base DomainContext.Invoke on DomainContext.InvokeAsync (#203)
- Invoke operation will now cancel only if the web request is cancelled (and then after cancellation)
Ensure Completed event is always called when Load/Invoke/SubmitOperation finishes (#206)
AuthenticationService is rewritten to use TPM (Task based methods) instead of APM for the methods implementing the actual authentication operations (#212, #214, #216)
Pass in endpoint name in WcfDomainClientFactory to make it easier to derive from it (#218)
Hosting - new "PubInternal" types
- behaviors for easy creation endpoints based on standard wcf (non REST) transports

Bugfix

Handle early cancellation (Cancellation before actual request has been sent) in WebDomainClient (#210)
- In earlier previews an exception was thrown instead of the operation beeing Cancelled

Server

Hosting - Endpoint changes (#218)
- Reuse the same ContractDescription for multiple endpoints (endpoint name is not longer added)
- Dont add SilverlightFaultBehaviour by default to DomainServices
- new "PubInternal" types
  - behaviors for easy creation endpoints based on standard wcf (non REST) transports
Trigger cancellation on client disconnect (#222)

Server

EntityFramework: Target IDbSet instead of DbSet with AttachAsModified extension methods (#215)

Infrastructure

Improved test execution times by reducing waiting delays (parts in #212. 213)

5.0.0 Preview 2

This is mostly a performance and feature update. It does not contain any new breaking changes since preiew 1

Client

Cache ChannelFactories for large performance improvements (#184)

Code generation

Code generation now works for netstandard and netcoreapp (#199, #201)
Fix error messages about incompatible Target frameworks when TargetFramework differs between client and server. (#188)

Server

Significant performance and memory usage improvemens for serialization (#189)
Improve Perf for Query and Invoke where validation is not required (#186)
Reduce per request allocations (#197)
Small improvements in Task To APM wrapper for async completing operations
Fix potential race condition when configuring endpoint authentication. (#196)

Other

Readme updates

5.0.0 Preview 1

Client

Most of the changes are Brekaing changes, even if many of them will only require changes in a small percentage of applications.

1 Change DomainClient contract to Task based async methods (#153) * Performing multiple loads and waiting for the result is now faster * Any custom DomainClient or code which interact with DomainClient will no longer compile. 2. Remove old target frameworks

Remove netstandard13 (#160)
Remove portable class library TargetFramework (#164)
Remove Silverlight (#174, #175 and more commits)
.Net Framework 4.5 requirement is replaced by 4.6 (will be 4.6.1+)

Move EntityList and QueryBuilder from OpenRiaServices...Data namespace to OpenRiaServices...Client namespace (#182)
Dont allocate PropertyChangedEventArgs if not needed (#155)
- remove sevaral OnPropertyChanged methods and only keep RaisePropertyChanged
  - If your code does not compile override RaisePropertyChanged instead
- Memory usage during Load etc is much lighter
Make DomainClientResult internal so it can be removed in the future
Have EntityContainer.LoadEntities return IEnumerable<Entity> instead of IEnumerable
Make WebDomainClient non sealed (#166) non breaking Make CallServiceOperation virtual so that the invoke behaviour can be modified in derived classes. This should simplify adding bearer based authentication
Cache WCF ChannelFactories per DomainContext type for improved perf (#184)

This significantly improves the performance for the first network operation per DominContext insteance. The cost is only paid on the first access per DomainService type (not per instance). Performance of overhead for E2E benchmark of loading some simple entity from a simple DomainService went from 200% to <10% (so the speedup for creating a new instance of this specific DomainContext is above 20 times) and will improve with more complex services.

Change from IEnumerable to IReadOnlyCollection in a few places (#183)

Mostly ValidationErrors properties and for IEntityCollection

Behaviour changes

Base DomainContext.Load on DomainContext.LoadAsync instead of other way around

The generic Load<TEntity> can be overridden but it will only be called when any of the "Load" methods are called

DomainContext.IsLoading is no longer set to false directly on cancellation. Instead a load is only considered done until after it has been cancelled (or completed)

Server

DomainServices are now async #159 and many methods have been renamed with Async suffic
Move aspnet authentication to separate namespace, assembly and nuget package (#173) Move Authenication related code from ..Server.ApplicationServices to

..Server.Authentication
and ..Server.Authentication.AspNetMembership (AuthenticationBase, UserBase ..)

- If you are using OpenRiaServices.EntityFramework the framework will now only call the SaveChangesAsync and not SaveChanges so if you are overriding SaveChanges make sure you do the same for SaveChangesAsync

Other

Fixed a number of flaky tests (#161, #172, .. and more commits)
use VS2019 for azure pipelines (#148)
Have client test start webserver if not already running (#169)
Changed folder structure by placing code in src folder (#176)
net45 dependency replaced with net46 dependency
- With slightly better less allocations as a result
Removed code market as obsolete (#170)
Some modernisation of codebase via refactoring via code analyzers

4.6.2

Client

Add transport (OpenRiaServices.DomainServices.Client.Web) to netstandard 2.0 nuget. This provides the SoapDomainClientFactory for netstandard / netcoreapp assemblies.

4.6.1

Client

Add new interface IEntityCollection (#156) This is a combination of ICollection<>, INotifyPropertyChanged, INotifyCollectionChanged as well as typed events for Add/Remove of entitites. It helps treating collections of entities EntityCollection and EntitySet in a more uniform way. It should help OpenRiaServices.M2M integrate better with the core pacakges.
LoadOperation performance improvements (Issue #154)

Raise Reset action instead of multiple Add notfications for significantly imroved IU responsiveness when binding to the Entitites or AllEntities properties before the load operation is completed.
- The UI now only updates once instead of potentially once per item
Don't allocate multiple NotifyCollectionChangedEventArgs and PropertyChangedEventArgs for each entity loaded.
Don't allocate event args if no one is listening

EntityCollection performance improvements (Issue #154)
- Don't allocate NotifyCollectionChangedEventArgs on each change if no one is listening

4.6.0

Client

Add netstandard 2.0 target
Support query translation for builtin VB operators in projects compiled using VS 2017
Support using "soap" endpoint from client (Cross Platform)

native support for all platforms supporting netstandard 2
Run this code before creating first DomainContext,

DomainContext.DomainClientFactory = new OpenRiaServices.DomainServices.Client.Web.SoapDomainClientFactory()
{
  ServerBaseUri = "https://my.site.com/",
};

Limitations / differences from binary endpoint:
- Standard query size limitations apply (no workaround as for binary endpoint)
- invoke operations will use POST even when for operations with HasSideEffect=false
- soap endpoint must be manually enabled on server

Server

Fix namespace for ObjectContextExtensions for OpenRiaServices.EntityFramework (breaking change)

Code generation

Other

Use VS 2017 for compilation
Replaced multiple projects with using built in multitargeting with SDK style projects
All assemblies are strong named ("signed") (#145)

The "signed" version of all nuget packages will be depreciated since it is only to replace them with the "normal" nuget packages
This will significantly make maintainance easier as well as make it easier to "get started" since there are less variations

Add VS Extension projects to main solution

Fix tests for VS Extension project
Remove "Interfaces" assembly to reduce complextity and fix some problems

Tooling

New Visual Studio extension https://marketplace.visualstudio.com/items?itemName=OpenRiaServices.OpenRiaServicesTooling release in preview
- Updates "manage openriaservices link" dialog with more settings
- Update add new item for domainservice item tempate so it generates EF6 compatible code
- Add VS2017 + VS2019 support
- Bugfix when invoking tooling with unloaded projects

4.5.4 and earlier

See: https://github.com/OpenRIAServices/OpenRiaServices/releases for release notes

Files

Changelog.md

Latest commit

History

Changelog.md

File metadata and controls

AspNetCore - 1.3.1

5.6.0 / AspNetCore 1.3.0

AspNetCore 1.3.0 (#518)

5.6.0

5.5.0 / EF Core 3.1.0 / AspNetCore 1.2.0

EF Core 3.1.0

AspNetCore 1.2.0

Code generation

Client

Client

AspNetCore 1.2.0

EF Core 3.0.0

5.4.3

Server

5.4.2 / AspNetCore 1.0.0

.NET8

Code generation

AspNetCore updates

Testhost

Other

5.4.1

Code generation

Client

Other

5.4.0

Code Generation Supports NET6+

Client

Other

AspNetCore 0.4.0

5.3.1 with EFCore 2.0.2 and AspNetCore 0.3.0

5.3.0 with EFCore 2.0.1

5.2.0

EFCore 2.0.0

AspNetCore 0.2.0

5.1.1

AspNetCore 0.1.1

5.1.0

Overview / Major features

What's new since 5.1.0-preview5

5.1.0-preview5

5.1.0-preview4

5.1.0-preview3

5.1.0-preview2

5.1.0-preview1

BinaryHttpDomainClientFactory

5.0.1

Infrastructure

5.0

Overview

Upgrade instructions

Samples

5.0.0 RC1

Client

Code Generation

Server

Unit Testing

5.0.0 Preview 3

Client

Server

Server

Infrastructure

5.0.0 Preview 2

Client

Code generation

Server

Other

5.0.0 Preview 1

Client

Server

Other

4.6.2

Client

4.6.1

Client