urfnet / URF.Core

Unit of Work & Repositories Framework - .NET Core, NET Standard, Entity Framework Core. 100% extensible & lightweight.

URF.Core   

^{Unit-of-Work & Repository Framework | Official URF, Trackable Entities & Design Factory Team}

Docs: URF.Core.Sample | Subscribe URF Updates: @lelong37 | NuGet: goo.gl/WEn7Jm

Sample & Live Demo w/ Source Code: URF.Core.Sample (Demo Site is down due to heavy traffic and Azure costs.)

URF.Core RTM is Complete!

URF.Core is feature complete and now has full parity with URF.NET (legacy .NET). URF.Core has gone through a complete rewrite with laser focus on Architecture, Design and Implementation as well as implementing top request for vNext, you can take a look at our URF.Core.Sample w/ ASP.NET Core Web API, OData, with full CRUD samples with Angular and Kendo UI.

Supported Added for MongoDb

As of version 3.1.1, support has been added for NoSQL Document databases with an implementation for MongoDb.

Samples for EF Core 3.x and MongoDb

Samples have been provided for EF Core 3.x and MongoDb.

Lightweight, Nano-Footprint

Staying faithful to (legacy) URF.NET of having a small footprint. URF.Core URF.Core (7 total classes) vs. URF.NET (12 total classes).

100% Extensible

We've made every implementation virtual therefore overridable for whatever teams/projects/developer use-cases as well as edge-cases.

IQuerable vs. IEnumerable

As as always, this is a religious debate between teams and the within the community. As with (legacy) URF.NET, we gave teams the option to opt into IQueryable or IEnumerable, and even both depending on your teams Architecture, Design & Implementation and style. As URF.NET and for teams that feel Repository Patterns that expose IQueryable as a leaky abstraction, simple use URF's IQuery API, which will give you all the Fluent features of IQueryable, however will return pure Entity or IEnumerable vs. using IQueryable, again URF.Core & URF.NET both support, so teams have the total freedom to choose which of the 3 paths/options makes most sense for their team/project.

URF.Core sample and usage in ASP.NET Core Web API & OData

public class ProductsController : ODataController
{
    private readonly IProductService _productService;
    private readonly IUnitOfWork _unitOfWork;

    public ProductsController(
        IProductService productService,
        IUnitOfWork unitOfWork)
    {
        _productService = productService;
        _unitOfWork = unitOfWork;
    }

    // e.g. GET odata/Products?$skip=2&$top=10
    [EnableQuery]
    public IQueryable<Products> Get() => _productService.Queryable();

    // e.g.  GET odata/Products(37)
    public async Task<IActionResult> Get([FromODataUri] int key)
    {
        if (!ModelState.IsValid)
            return BadRequest(ModelState);

        var product = await _productService.FindAsync(key);

        if (product == null)
            return NotFound();

        return Ok(product);
    }

    // e.g. PUT odata/Products(37)
    public async Task<IActionResult> Put([FromODataUri] int key, [FromBody] Products products)
    {
        if (!ModelState.IsValid)
            return BadRequest(ModelState);

        if (key != products.ProductId)
            return BadRequest();

        _productService.Update(products);

        try
        {
            await _unitOfWork.SaveChangesAsync();
        }
        catch (DbUpdateConcurrencyException)
        {
            if (!await _productService.ExistsAsync(key))
                return NotFound();
            throw;
        }

        return NoContent();
    }

    // e.g. PUT odata/Products
    public async Task<IActionResult> Post([FromBody] Products products)
    {
        if (!ModelState.IsValid)
            return BadRequest(ModelState);

        _productService.Insert(products);
        await _unitOfWork.SaveChangesAsync();

        return Created(products);
    }

    // e.g. PATCH, MERGE odata/Products(37)
    [AcceptVerbs("PATCH", "MERGE")]
    public async Task<IActionResult> Patch([FromODataUri] int key, [FromBody] Delta<Products> product)
    {
        if (!ModelState.IsValid)
            return BadRequest(ModelState);

        var entity = await _productService.FindAsync(key);
        if (entity == null)
            return NotFound();

        product.Patch(entity);
        _productService.Update(entity);

        try
        {
            await _unitOfWork.SaveChangesAsync();
        }
        catch (DbUpdateConcurrencyException)
        {
            if (!await _productService.ExistsAsync(key))
                return NotFound();
            throw;
        }
        return Updated(entity);
    }

    // e.g. DELETE odata/Products(37)
    public async Task<IActionResult> Delete([FromODataUri] int key)
    {
        if (!ModelState.IsValid)
            return BadRequest(ModelState);

        var result = await _productService.DeleteAsync(key);

        if (!result)
            return NotFound();

        await _unitOfWork.SaveChangesAsync();

        return StatusCode((int) HttpStatusCode.NoContent);
    }
}

Performance

URF.Core has been completely re-written, and everything is now completely task, async, await right out of the box. This way, teams will automatically get the best thread management out on asynchronous perf improvements.

URF Powered & Sponsered by:

© 2017 URF.NET All rights reserved.