The temporary location used for caches is a sub-directory named dotnet-script under (in order of priority): You can override this automatic caching by passing -no-cache flag, which will bypass both caches and cause dependency resolution and script compilation to happen every time we execute the script. If the hashes don't match, the cache is invalidated and we recompile. If they match there is no need to recompile and we run from the already compiled DLL. When a script is executed the hash is computed and compared with the hash from the previous compilation. This hash is written to a temporary location along with the DLL that represents the result of the script compilation. This works by creating a SHA256 hash from all the script files involved in the execution.
#Script it download code#
In order to execute a script it needs to be compiled first and since that is a CPU and time consuming operation, we make sure that we only compile when the source code has changed. If any of the dependencies has changed, we must restore again to obtain the new dependency graph. If these dependencies matches the dependencies from the last script execution, we skip the restore and read the dependencies from the already generated file. So this cache works by looking at all the dependencies specified in the script(s) either in the form of NuGet package references or assembly file references. This is an out-of-process operation and represents a significant overhead to the script execution.
In order to resolve the dependencies for a script, a dotnet restore is executed under the hood to produce a file from which we can figure out all the dependencies we need to add to the compilation. The reason for this constraint is that we need to make sure that we don't execute a script with a stale dependency graph. In order for any of these caches to be enabled, it is required that all NuGet package references are specified using an exact version number. We provide two types of caching, the dependency cache and the execution cache which is explained in detail below.
0 kommentar(er)
