dotConnect for Google BigQuery Documentation
On this page
    Deployment
    On this page

    To deploy applications written with dotConnect for Google BigQuery, you should register run-time assemblies Devart.Data.BigQuery.dll, Devart.Data.SqlShim.dll, and Devart.Data.dll in the Global Assembly Cache (GAC) for the appropriate framework or place them in the folder of your application (Bin folder for web projects). These three assemblies should be available in all applications written with dotConnect for Google BigQuery. Activate dotConnect for Google BigQuery on the target computer, or pass the activation key at run time as described in Activation.

    Your application should also have access to the sqlite3.dll library. This library can be located either in the application folder or in a system-wide accessible folder. The bitness (32-bit or 64-bit) of the library must correspond to the bitness of your application.

    When your code uses dotConnect for Google BigQuery via a factory-based class, you should register configuration information in the DbProviderFactories section of the *.config file to inform your environment about the existence of the provider factory. The provider factory is described either in machine.config (globally), in app.config, or in web.config (just for your application). This is done as follows:

    <system.data>
      <DbProviderFactories>
        <remove invariant="Devart.Data.BigQuery" />
        <add name="dotConnect for Google BigQuery" invariant="Devart.Data.BigQuery" description="Devart dotConnect for Google BigQuery" type="Devart.Data.BigQuery.BigQueryProviderFactory, Devart.Data.BigQuery, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />
      </DbProviderFactories>
    </system.data>
    

    Replace 1.0.0.0 here with your actual version.

    Continuous Integration

    If you set up a pipeline for compiling your source code from a repository on a build server periodically or even after every commit, you should add a step to your pipeline for installing the provider on the build server, copying Devart.* assemblies, and registering the provider build action. For example, the corresponding step in Azure DevOps Pipeline can be the following one if you copied the provider installation to the root folder of your repository:

    - task: CmdLine@2
      inputs:
        script: '$(Build.SourcesDirectory)\dcbigquery.exe /TYPE=FULL /VERYSILENT'
    

    For more information about the command line installation keys, see Installation.

    Required Permissions

    When a dotConnect for Google BigQuery application is used in a partially trusted environment (which may apply to certain ASP.NET applications), it requires at least medium trust.

    Since dotConnect for Google BigQuery uses standard Microsoft .NET licensing, it additionally requires RegistryPermission. Although SecurityPermission is granted by default at the medium trust level, the set of flags for SecurityPermission must be extended. You need to add the following flags: Assertion, SkipVerification, UnmanagedCode, and SerializationFormatter.

    For information on how to do this, see Configuring Trust Level for Web Applications.

    Entity Framework Core Projects

    When deploying Entity Framework Core projects, make sure that the Devart.Data.BigQuery.EFCore.dll assembly is available for your application. The Devart.Data.BigQuery.EFCore NuGet package adds it and copies it to the application's output folder.

    For Entity Framework Core there is no need to register the provider in the machine.config file.