Compiling/running test project offline

[willson-chen]

I executed command dotnet run -c Release -f netcoreapp2 -p test/ICSharpCode.SharpZipLib.TestBootstrapper/ICSharpCode.SharpZipLib.TestBootstrapper.csproj in offline environment, and got the follow errors.

/root/dotnet/sdk/2.1.808/NuGet.targets(123,5): error : Unable to load the service index for source https://api.nuget.org/v3/index.json. [/data/sharpziplib_test/SharpZipLib-master/src/ICSharpCode.SharpZipLib/ICSharpCode.SharpZipLib.csproj]
/root/dotnet/sdk/2.1.808/NuGet.targets(123,5): error :   The HTTP request to 'GET https://api.nuget.org/v3/index.json' has timed out after 100000ms. [/data/sharpziplib_test/SharpZipLib-master/src/ICSharpCode.SharpZipLib/ICSharpCode.SharpZipLib.csproj]

It seems that the erros were caused by Internet disconnection. Is there a way to compile SharpZipLib offline, please?

[Numpsy]

It might work if you have the packages it needs in the nuget package cache, otherwise i'm not sure, short of pointing the build at a local package source?

[piksel]

Not really sharpziplib-specific, but you can use --no-restore to prevent dotnet from trying to restore packages on run.

[willson-chen]

@piksel @Numpsy Thanks for your reply，now build offline could succeed by add --no-restore.
I want to know whether the test command dotnet run -c Debug -f netcoreapp2 -p test/ICSharpCode.SharpZipLib.TestBootstrapper/ICSharpCode.SharpZipLib.TestBootstrapper.csproj could also be executed offline with similar options?

[piksel]

If it is already built, it shouldn't need to build/restore again when running, but you can specify either --no-build or --no-restore to dotnet run as well. The arguments are documented in the dotnet command help:

x00 $ dotnet run --help
Usage: dotnet run [options] [[--] <additional arguments>...]]

Options:
  -h, --help                            Show command line help.
  -c, --configuration <CONFIGURATION>   The configuration to run for. The default for most projects is 'Debug'.
  -f, --framework <FRAMEWORK>           The target framework to run for. The target framework must also be specified in the project file.
  -r, --runtime <RUNTIME_IDENTIFIER>    The target runtime to run for.
  -p, --project                         The path to the project file to run (defaults to the current directory if there is only one project).
  --launch-profile                      The name of the launch profile (if any) to use when launching the application.
  --no-launch-profile                   Do not attempt to use launchSettings.json to configure the application.
  --no-build                            Do not build the project before running. Implies --no-restore.
  --interactive                         Allows the command to stop and wait for user input or action (for example to complete authentication).
  --no-restore                          Do not restore the project before building.
  -v, --verbosity <LEVEL>               Set the MSBuild verbosity level. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].
  --no-dependencies                     Do not restore project-to-project references and only restore the specified project.
  --force                               Force all dependencies to be resolved even if the last restore was successful.
                                        This is equivalent to deleting project.assets.json.
Additional Arguments:
  Arguments passed to the application that is being run.