v5.5.0 / EntityFrameworkCore 3.1.0 / AspNetCore 1.2.0
OpenRiaServices.EntityFrameworkCore 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 onDbSet
but- is smarter (works with and without original entity)
- reduces code that needs to be written and works both with and without "OriginalEntity" (
RoundTripAttribute
)
- It works similar to the existing
- 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 ServicesSome-Namespace-TypeName.svc/binary/Method
FullName
will generate routes with the full name of the DomainServiceSome-Namespace-TypeName/Method
Name
will generate routes with the short name of the DomainServiceTypeName/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
- The client currently detect
BinaryHttpDomainClientFactory
has a new constructor taking in anFunc<Uri, HttpClient>
so that the callback has access to the uri passed to the DomainContext- If the HttpClient factory method sets
BaseAddress
on the httpClient then the address vill be preserved and used for server calls.
- If the HttpClient factory method sets
What's Changed
- T4 codegen does not add compiler attributes by @SandstromErik in #495
- Add EF Core 8 support by @Daniel-Svensson in #496
- Remove ProjectPath.txt from tests by @Daniel-Svensson in #494
- Improve error messages from code generation by @Daniel-Svensson in #499
- Analyser fixes and update nuget.exe version by @Daniel-Svensson in #501
- Log whole Exceptions in DomainServiceCatalog instead of just message by @Daniel-Svensson in #502
- Call "dotnet CodeGenTask.dll" instead of "CodeGenTask.exe" by @Daniel-Svensson in #503
- Add AttachAsXXX methods to DbDomainService: by @SandstromErik in #506
- EF Core: Owned types support by @Daniel-Svensson in #500
- Replace obsolete AssociationAttribute with new EntityAssociationAttribute on client by @Daniel-Svensson in #509
- EntityAssociationAttribute Step2 by @Daniel-Svensson in #513
- Add Obsolete (things not used on AspNetCore) or by codegen by @Daniel-Svensson in #511
- AspNetCore: Enable shorter Uris by @Daniel-Svensson in #508
Full Changelog: v5.4.3...v5.5.0