The F# Type Provider SDK

The F# Type Provider SDK is two things:

1. The ProvidedTypes.fs API files you need to author type providers

2. Documentation and samples on type provider creation

Getting Started

To create a type provider use:

dotnet new -i FSharp.TypeProviders.Templates
dotnet new typeprovider -n LemonadeProvider -lang F#

The template uses paket to acquire the files of the latest published type provider SDK.

cd LemonadeProvider

dotnet tool restore
dotnet paket update
dotnet build -c release

dotnet test -c release

The type provider also contains the logic necessary to package the type provider:

dotnet paket pack nuget --version 0.0.1

The ProvidedTypes API - A Basic Type Provider

When you instantiate the template above you get basic erasing and geneative type providers.

Some unit testing helpers

The SDK includes a file

• ProvidedTypesTesting.fs

which is sometimes incorporated into a type provider to help enable unit testing. For examples of how this is used, see uses of the helpers in the FSharp.Data library such as:

• Testing.GenerateProvidedTypeInstantiation
• Targets.DotNetStandard20FSharpRefs to get a suitable set of references for .NET Standard plus the running FSharp.Core
• Testing.FormatProvidedType to get a textual representation of a provided type, used to "snapshot" the full description of expected type generation

Sometimes unit test DLLs incorporate the entire type provider implementation, and sometimes they use InternalsVisibleTo.

The unit testing helpers aren't really an official, documented part of the DK - caveat emptor.

Examples

See examples the examples directory.

Type Provider Naming Conventions

A type provider is simultaneously a tool and a library. The existing guidance is as follows, from https://fsharp.github.io/2014/09/19/fsharp-libraries.html.

Likewise, a type provider for a data source or schema format XYZ should normally be placed in “FSharp.Data”, e.g. “FSharp.Data.XYZ”.

Good type provider naming examples:

• FSharp.Text.RegexProvider
• FSharp.Azure.StorageTypeProvider

Existing type providers that don't quite follow the guidelines but which are ok:

• FSharp.Data

Here are some examples of existing type providers that aren't too bad (they are clear) but could be renamed to follow the guidelines:

• ExcelProvider (better would be FSharp.Interop.ExcelProvider)
• RProvider (better would be FSharp.Interop.RProvider)
• ApiaryProvider (better would be FSharp.Data.ApiaryProvider)
• SQLProvider (better would be FSharp.Data.SQLProvider)
• DynamicsNAVProvider (better would be FSharp.Interop.DynamicsNAVProvider)
• DynamicsCRMProvider (better would be FSharp.Interop.DynamicsCRMProvider)

Technical Notes

Using Type Providers with dotnet build

Correctly updated type providers can be used with either the dotnet toolchain (.NET SDK tools which executes using .NET Core) or msbuild (traditional .NET Framework/Mono) toolchain.

Nuget package layouts you should use

The typical nuget package layout for a very simple provider that has combined design-time and runtime components and no dependencies is:

lib/netstandard2.0
    MyProvider.dll // acts as both TPRTC and TPDTC

The typical nuget package layout for a provider that has separate design-time and runtime components is like this. You should also likely use this if your type provider has any extra dependencies.

lib/netstandard2.0
    MyProvider.dll // TPRTC

typeproviders/fsharp41/
    netstandard2.0/
        MyProvider.DesignTime.dll // TPDTC
        MyDesignTimeDependency.dll // bundled dependencies of TPDTC

Runtime dependencies are often the same as design time dependencies for simple type providers. For more complex providers these can be different

• The runtime dependencies are the dependencies of everything in your quotations in your type provider implementation.

• The design dependencies are the dependencies of everything outside the quotations to decide and generate the provided types.

These dependencies are packaged and managed differently

• The runtime dependencies are normal nuget package dependencies just like any normal .NET library. FOr example, if your type provider has Newtonsoft.Json as a runtime dependency then your nuget package should list this a normal nuget dependency.

• The design dependencies must all be bundled alongside your design-time DLL. The design-time component is a component loaded into a tool like Ionide or Visual Studio and must be loadable without referencing any other packages.

Lifetime of type provider instantiations

F# type providers are hosted by applications using FSharp.Compiler.Service. These notes describe the lifetime and typical resource usage of type provider instances for applications that incorporate FSharp.Compiler.Service (the host). Most documentation on the compiler as a service can be found at http://github.com/fsharp/FSharp.Compiler.Service.

Each time the host application (e.g. devenv.exe) checks a file using type providers (e.g. containing JsonProvider<"...">), one or more new TP instantiations may be created, along with subsequent calls to ApplyStaticArguments.

• The F# compiler service doesn't try to cache these (except where it caches the TAST structures that results of checking a file or project).

• Individual type providers may use caching of some kind, returning previous provided types when the type provider is instantiated the same way. Care should be taken that these caches do not permanently occupy resources

• Under the hood, the majority of resources used by a TP instantiation are those required to "map" the generated types to the referenced assemblies. To support this, each TP Instantiation creates one ILModuleReader for each referenced assembly. When the compiler is used as a service, the natural (minimal) lifetime of a ILModuleReader is the same as its TP Instanatiation. The TPSDK may share these resources.

• The natural (i.e. minimal) lifetime of a TP Instantiation and its related objects (ProvidedType ProvidedMethodInfo etc. etc. ) is the same as the TAST structures which refer these things (TProvidedTypeInfo, MethInfo, FieldInfo from infos.fs).

The lifetime of TAST structures is as long as they are held in the IncrementalBuilder, or you hold on to FSharpCheckFileResults, or FSharpCheckProjectResults, or FSharpAssemblyContents.

FAQ

How do I debug execution of a type provider when using .NET Framework tools on Windows?

1. Capture output of msbuild -v:n in args.txt and trim out the rubbish leaving just the command line arguments to the F# compiler, usually starting with -o:...

2. Run an explicit invocation of the compiler using this, checking that your failures still happen

   fsc.exe @args.txt
   

   Then debug that invocation using

   devenv /debugexe fsc.exe @args.txt
   

   If your failures only happen in the IDE then use devenv /debugexe devenv.exe MyProj.fsproj, set debug type to ".NET Framework 4.0" and launch F5. Likewise if your failures only happen in F# Interactive then use devenv /debugexe fsi.exe MyProj.fsproj.

   Set first-catch exception handling (Ctrl-Alt-E, select all CLR exceptions) and set Just My Code off

A dependency of my type provider is not loading, what do I do?

For example, let's say you have this error in your test project:

2>E:\GitHub\admin\joe-provider\test\Joe.Test\ProviderTests.fs(8,10): error FS3033: The type provider 'Joe.Provider.JoeProvider' reported an error: Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed'. The system cannot find the file specified. [E:\GitHub\dsyme\joe-provider\test\Joe.Test\Joe.Test.fsproj]

Here your test project is referencing your provider project, and your type provider has a dependency on Newtonsoft.Json.dll. To see what's going on, run

dotnet build -v:n

In the compilation of your test project you will see something like this:

     C:\Program Files\dotnet\dotnet.exe "C:\Program Files\dotnet\sdk\3.1.401\FSharp\fsc.exe"
         -o:obj\Debug\netcoreapp3.1\Joe.Test.dll
         ...
         -r:E:\GitHub\admin\joe-provider\src\Joe.Provider\bin\Debug\netstandard2.0\Joe.Provider.dll
         ...

1. The tool fsc.exe is trying to load the type provider but a dependency is not found. As mentioned above, all dependencies must be packaged alongside your design time component. For example, adding

   <Content Include="..\..\packages\Newtonsoft.Json\lib\netstandard2.0\Newtonsoft.Json.dll" CopyToOutputDirectory="PreserveNewest" />
   

   will include the component and unblock you. However, you will need to be careful to make sure this component is laid down in the right place in your nuget package, see the instructions above for what the final layout of the nuget package should be.

2. When making type providers whose design-time components have dependencies, you should always use a "split" type provider that separates the design-time and runtime components.

TODO: give exact .fsproj/nuget instructions to get the dependency into the typeproviders\fsharp41\netstandard2.0 directory alongside the design-time component.

How do I debug execution of a type provider when using .NET Core tools on Windows?

One approach:

1. Capture output of dotnet build -v:n in args.txt and trim out the rubbish leaving just the command line arguments to the F# compiler, usually starting with -o:...

2. Run an explicit invocation of the compiler using:

   "c:\Program Files\dotnet\dotnet.exe" "C:\Program Files\dotnet\sdk\2.1.403\FSharp\fsc.exe" @args.txt
   

   Then debug that invocation using

   devenv /debugexe "c:\Program Files\dotnet\dotnet.exe" "C:\Program Files\dotnet\sdk\2.1.403\FSharp\fsc.exe" @args.txt
   

   Be careful to make sure Visual Studio debugging type is set to ".NET Core" (right click properties on dotnet and set debug type)

   Set first-catch exception handling (Ctrl-Alt-E, select all CLR exceptions) and set Just My Code off.

Some Type Provider terminology

• TPRTC - Type Provider Run Time Component, e.g. FSharp.Data.dll.

  • This is the component referenced by #r or -r: on the command line or other configration of a host tool

  • May be the same physical file as the TPDTC.

  • Contains either a TypeProviderAssembly() attribute indicating that this component is also a TPDTC, or TypeProviderAssembly("MyDesignTime.dll") attribute indicating that the name of the design time component.

  • A type provider package may have multiple such DLLs for different target platforms, e.g.

    lib\net45\FSharp.Data.dll
    lib\netstandard2.0\FSharp.Data.dll
    

  • TPRTCs are normally .NET Framework 4.x, .NET Standard 2.0 or some portable profile component.

• TPDTC - Type Provider Design Time Component, e.g. FSharp.Data.DesignTime.dll.

  • The DLL that gets loaded into host tools.

  • May be the same physical file as the TPRTC.

  • This component includes the ProvidedTypes.fs/fsi files from the type provider SDK.

  • TPDTCs are currently .NET Framework 4.x. They can also be .NET Standard 2.0 components, see below

• Host tool - Either fsc.exe, fsi.exe or some tool hosting FSharp.Compiler.Service.dll such as devenv.exe or FsAutoComplete.exe

How the TPDTC is found and loaded

Currently, host tools look for TPDTC DLLs alongside the TPRTC DLL. For simple type providers, these DLLs are the same. When executing using .NET Framework, the host tool uses Assembly.LoadFrom to load this component.

See Type provider design-time DLLs should be chosen more appropriately for a proposal to change the rules to allow TPDTC components to be found more usefully, and in particular for different TPDTC components to be loaded depending on the execution environment of the host tooling.

Explicit construction of code: MakeGenericType, MakeGenericMethod and UncheckedQuotations

Some type providers need to build code via explicit calls to FSharp.Quotations.Expr.* rather than via quotation literals. Frequently, this is needed when code must instantiate generic methods or types. However, in some cases limitations of the F# quotations API are reached.

In these cases, follow these rules

1. Always use ProvidedTypeBuilder.MakeGenericType(type, typeArguments) rather than type.MakeGenericType(typeArguments)
2. Always use ProvidedTypeBuilder.MakeGenericMethod(methInfo, methTypeArguments) rather than methInfo.MakeGenericType(methTypeArguments)
3. Where necessary open open ProviderImplementation.ProvidedTypes.UncheckedQuotations and make quotation nodes representing calls and other operations using Expr.CallUnchecked.

If you don't do this you may get errors like

The type provider 'FSharp.Configuration.ConfigTypeProvider+FSharpConfigurationProvider' reported an error: Type mismatch when building 'args': invalid parameter for a method or indexer property. Expected 'System.Collections.Generic.IEnumerable`1[System.String]', but received type 'System.Collections.Generic.IEnumerable`1[System.String]'.�Parameter name: receivedType

or

System.InvalidOperationException: the operation is not valid due to the current state of the object. at System.Reflection.MemberInfo.get_MetadataToken() in f:\dd\ndp\clr\src\BCL\system\reflection\memberinfo.cs:line 65

Resources

For advice on how to get started building a type provider, check out:

• Type Providers from the ground up
• (and the follow up posts)
• The MSDN Tutorial. The code in this package replaces the code from the sample pack it mentions.

Support and community

• If you have a question about FSharp, ask at StackOverflow and mark your question with the f# tag.
• If you want to submit a bug, a feature request or help with fixing bugs then look at issues.
• To discuss more general issues about F# Type Providers SDK, its goals and other open-source F# projects, join the fsharp-opensource mailing list

Building

Use

build.sh RunTests

or

build.cmd RunTests

Library license

The library is available under the MIT License. For more information see the License file in the GitHub repository.

Maintainer(s)

• @mavnn
• @ovatsus
• @dsyme
• @cartermp

The default maintainer account for projects under "fsprojects" is @fsprojectsgit - F# Community Project Incubation Space (repo management)