Explicitly run first-time experience

Hi,

I’m automating the creation of virtual machines that will be used as build servers.

After installing the .NET Core SDK through the Visual Studio 2017 Installer, the first-time experience does not appear to be run. Thus, on the first build that happens on that server, that build includes the first-run experience.

Since my build process attempts to build multiple projects in parallel, various instances of dotnet choke over the first-use sentinel when attempting concurrent writes:

Welcome to .NET Core!
---------------------
Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://aka.ms/dotnet-cli-docs.

Telemetry
--------------
The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include command-line arguments. The data is collected by Microsoft and shared with the community.
You can opt out of telemetry by setting a DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 using your favorite shell.
You can read more about .NET Core tools telemetry @ https://aka.ms/dotnet-cli-telemetry.

My.DotNet.Project.dll (net47) ExitCode = 1
System.IO.IOException: The process cannot access the file 'C:\Users\BuildServerUser\.dotnet\2.1.104.dotnetFirstUseSentinel' because it is being used by another process.
   at System.IO.FileStream.OpenHandle(FileMode mode, FileShare share, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
   at System.IO.File.Create(String path)
   at Microsoft.Extensions.EnvironmentAbstractions.FileWrapper.CreateEmptyFile(String path)
   at Microsoft.DotNet.Configurer.FirstTimeUseNoticeSentinel.CreateIfNotExists()
   at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.PrintFirstTimeUseNotice()
   at Microsoft.DotNet.Configurer.DotnetFirstTimeUseConfigurer.Configure()
   at Microsoft.DotNet.Cli.Program.ConfigureDotNetForFirstTimeUse(INuGetCacheSentinel nugetCacheSentinel, IFirstTimeUseNoticeSentinel firstTimeUseNoticeSentinel, CliFallbackFolderPathCalculator cliFallbackFolderPathCalculator)
   at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient)
   at Microsoft.DotNet.Cli.Program.Main(String[] args)

Is there a sensible way to kick off this process automatically at the time that the VM is created, rather than at the time of the first build? I’d rather do it eagerly than lazily.

Thanks.

[vcsjones]

Seems like this is a dupe of dotnet/sdk#7293.

[livarcocc]

Agreed.