EntityFrameworkCore.FSharp 6.0.5

There is a newer version of this package available.
See the version list below for details.
dotnet add package EntityFrameworkCore.FSharp --version 6.0.5                
NuGet\Install-Package EntityFrameworkCore.FSharp -Version 6.0.5                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="EntityFrameworkCore.FSharp" Version="6.0.5" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add EntityFrameworkCore.FSharp --version 6.0.5                
#r "nuget: EntityFrameworkCore.FSharp, 6.0.5"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install EntityFrameworkCore.FSharp as a Cake Addin
#addin nuget:?package=EntityFrameworkCore.FSharp&version=6.0.5

// Install EntityFrameworkCore.FSharp as a Cake Tool
#tool nuget:?package=EntityFrameworkCore.FSharp&version=6.0.5                

EFCore.FSharp

Add F# design time support to EF Core.

For a basic introduction to running code-first migrations, please see the getting started guide.


Builds

Build Status

NuGet

Package Stable Prerelease
EFCore.FSharp NuGet Badge NuGet Badge

Usage

Install the package from NuGet and follow our Getting Started guide or our full documentation at https://efcore.github.io/EFCore.FSharp

Currently created migrations must be manually added to your solution in the correct order. Although migrations are created with sequential file names so a glob can also be used

<Compile Include="Migrations/*.fs" />

Building

> build.cmd <optional buildtarget> // on windows
$ ./build.sh  <optional buildtarget>// on unix

After building the solution, it will create a NuGet package in the dist folder. This can then be referenced as usual.

Developing

Make sure the following requirements are installed on your system:

or


Environment Variables

  • CONFIGURATION will set the configuration of the dotnet commands. If not set, it will default to Release.
    • CONFIGURATION=Debug ./build.sh will result in -c additions to commands such as in dotnet build -c Debug
  • GITHUB_TOKEN will be used to upload release notes and Nuget packages to GitHub.
    • Be sure to set this before releasing
  • DISABLE_COVERAGE Will disable running code coverage metrics. AltCover can have severe performance degradation so it's worth disabling when looking to do a quicker feedback loop.
    • DISABLE_COVERAGE=1 ./build.sh


Build Targets

  • Clean - Cleans artifact and temp directories.
  • DotnetRestore - Runs dotnet restore on the solution file.
  • DotnetBuild - Runs dotnet build on the solution file.
  • DotnetTest - Runs dotnet test on the solution file.
  • GenerateCoverageReport - Code coverage is run during DotnetTest and this generates a report via ReportGenerator.
  • WatchTests - Runs dotnet watch with the test projects. Useful for rapid feedback loops.
  • GenerateAssemblyInfo - Generates AssemblyInfo for libraries.
  • DotnetPack - Runs dotnet pack. This includes running Source Link.
  • SourceLinkTest - Runs a Source Link test tool to verify Source Links were properly generated.
  • PublishToNuGet - Publishes the NuGet packages generated in DotnetPack to NuGet via paket push.
  • GitRelease - Creates a commit message with the Release Notes and a git tag via the version in the Release Notes.
  • GitHubRelease - Publishes a GitHub Release with the Release Notes and any NuGet packages.
  • FormatCode - Runs Fantomas on the solution file.
  • BuildDocs - Generates Documentation from docsSrc and the XML Documentation Comments from your libraries in src.
  • WatchDocs - Generates documentation and starts a webserver locally. It will rebuild and hot reload if it detects any changes made to docsSrc files, libraries in src, or the docsTool itself.
Product Compatible and additional computed target framework versions.
.NET net5.0 is compatible.  net5.0-windows was computed.  net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories (2)

Showing the top 2 popular GitHub repositories that depend on EntityFrameworkCore.FSharp:

Repository Stars
linq2db/linq2db
Linq to database provider.
linq2db/linq2db.EntityFrameworkCore
Bring power of Linq To DB to Entity Framework Core projects
Version Downloads Last updated
6.0.7 25,705 6/26/2022
6.0.6 4,792 1/16/2022
6.0.5 807 11/30/2021
6.0.4 1,382 11/29/2021
6.0.3 1,012 11/21/2021
6.0.2 683 11/13/2021
6.0.1 644 11/10/2021
6.0.0 608 11/9/2021
5.0.3 2,982 10/16/2021
5.0.3-beta006 1,510 8/17/2021
5.0.3-beta005 515 8/9/2021
5.0.3-beta004 715 6/16/2021
5.0.3-beta003 1,506 5/27/2021
5.0.3-beta002 576 5/12/2021
5.0.3-beta001 658 5/8/2021
5.0.3-alpha9 645 4/6/2021
5.0.3-alpha8 554 4/4/2021
5.0.3-alpha7 552 4/1/2021
5.0.3-alpha6 520 4/1/2021
5.0.3-alpha5 527 3/31/2021
5.0.3-alpha3 487 3/31/2021
5.0.3-alpha2 573 3/27/2021
5.0.3-alpha10 559 4/18/2021
5.0.3-alpha1 556 3/21/2021

## [6.0.5] - 2021-11-30

[6.0.5]: https://github.com/efcore/EFCore.FSharp/compare/v6.0.4...v6.0.5

### Fixed
- AlterColumn operations no longer emit compiler warnings - https://github.com/efcore/EFCore.FSharp/pull/125

### Known Issues
- AlterColumn operations are being created in what should be empty migrations. No effect on functionality but shouldn't be happening - associated issue - https://github.com/efcore/EFCore.FSharp/issues/126