Team Drives-related fields in the Vault API are being replaced. Learn more.

.NET quickstart

Complete the steps described in the rest of this page to create a simple .NET console application that makes requests to the Google Vault API.

Prerequisites

To run this quickstart, you need the following prerequisites:

  • Authorization credentials for a desktop application. To learn how to create credentials for a desktop application, refer to Create credentials.
* A Google account

Step 1: Prepare the project

  1. Create a new Visual C# Console Application project in Visual Studio.
  2. Open the NuGet Package Manager Console, select the package source nuget.org, and run the following command:
Install-Package Google.Apis.Vault.v1

Step 2: Set up the sample

  1. Drag credentials.json, downloaded as a prerequisite, into your Visual Studio Solution Explorer.
  2. Select credentials.json, and then go to the Properties window and set the Copy to Output Directory field to Copy always.
  3. Replace the contents of Program.cs with the following code:

vault/VaultQuickstart/VaultQuickstart.cs
using Google.Apis.Auth.OAuth2;
using Google.Apis.Vault.v1;
using Google.Apis.Vault.v1.Data;
using Google.Apis.Services;
using Google.Apis.Util.Store;
using System;
using System.Collections.Generic;
using System.IO;
using System.Linq;
using System.Text;
using System.Threading;
using System.Threading.Tasks;

namespace VaultQuickstart
{
    class Program
    {
        // If modifying these scopes, delete your previously saved credentials
        // at ~/.credentials/vault.googleapis.com-dotnet-quickstart.json
        static string[] Scopes = { VaultService.Scope.EdiscoveryReadonly };
        static string ApplicationName = "Google Vault API .NET Quickstart";

        static void Main(string[] args)
        {
            UserCredential credential;

            using (var stream =
                new FileStream("credentials.json", FileMode.Open, FileAccess.Read))
            {
                // The file token.json stores the user's access and refresh tokens, and is created
                // automatically when the authorization flow completes for the first time.
                string credPath = "token.json";
                credential = GoogleWebAuthorizationBroker.AuthorizeAsync(
                    GoogleClientSecrets.Load(stream).Secrets,
                    Scopes,
                    "user",
                    CancellationToken.None,
                    new FileDataStore(credPath, true)).Result;
                Console.WriteLine("Credential file saved to: " + credPath);
            }

            // Create Vault API service.
            var service = new VaultService(new BaseClientService.Initializer()
            {
                HttpClientInitializer = credential,
                ApplicationName = ApplicationName,
            });

            // Define request parameters.
            MattersResource.ListRequest request = service.Matters.List();
            request.PageSize = 10;

            // List matters.
            ListMattersResponse response = request.Execute();
            Console.WriteLine("Matters:");
            if (response.Matters != null && response.Matters.Count > 0)
            {
                foreach (var matter in response.Matters)
                {
                    Console.WriteLine("{0} ({1})", matter.Name, matter.MatterId);
                }
            }
            else
            {
                Console.WriteLine("No matters found.");
            }
            Console.Read();

        }
    }
}

Step 3: Run the sample

Build and run the sample by clicking Start in the Visual Studio toolbar.

The first time you run the sample, it prompts you to authorize access:

  1. The sample attempts to open a new window or tab in your default browser. If this fails, copy the URL from the console and manually open it in your browser.

    If you're not already signed in to your Google account, you're prompted to sign in. If you're signed in to multiple Google accounts, you're asked to select one account to use for authorization.

  2. Click the Accept button.
  3. The sample proceeds automatically, and you may close the window/tab.

Notes

  • Authorization information is stored on the file system, so subsequent executions won't prompt for authorization.
  • The authorization flow in this example is designed for a command-line application. For information on how to perform authorization in a web application, see the web applications section of the library's OAuth 2.0 guide.

Troubleshooting

This section describes some common issues that you may encounter while attempting to run this quickstart and suggests possible solutions.

Could not load file or assembly 'Microsoft.Threading.Tasks'

This error can occur when using an outdated or incorrectly installed version of the Microsoft.Bcl.Async package. Reinstall the package using the following command in the NuGet Package Manager Console:

Update-Package Microsoft.Bcl.Async -reinstall

You are prompted to restart Visual Studio to complete the installation.

This app isn't verified

If the OAuth consent screen displays the warning "This app isn't verified," your app is requesting scopes that provide access to sensitive user data. If your application uses sensitive scopes, your your app must go through the verification process to remove that warning and other limitations. During the development phase you can continue past this warning by clicking Advanced > Go to {Project Name} (unsafe).

Further reading