Hi Gianni,

Yeah when you are developing a site those files now come from your local .nuget cache folder but aspnet core uses FileProviders to make it look like they are coming from the site.

Via Javascript

if your plugin is using these files from JavaScript then in theory accessing them should still work because the browser will still think they are in the same location.

e.g - this code uses the assetService to load the jsDiff library (and works in v10)

var jsdiff = 'lib/jsdiff/diff.js';

assetsService.loadJs(jsdiff, $scope).then(function () {
    calcDiffs();
});

but do check you have the right URL as some files have also changed for example the jsdiff library path has changed from lib/jsdiff/diff.min.js to lib/jsdiff/diff.js subtle but will cause you problems.

Via c# code

If your plugin is accessing files in the folder from c# then you need to switch over to using the FileProvider to locate the files (as opposed to System.IO.File libraries - because the files aren't really there but the file provider makes it look like they are.

If you use the FileProvider from IWebHostEnvironment.

e.g (also note i haven't tested this code. but its something like this)

var fileProvider = webHostEnvironment.WebRootFileProvider;
var fileInfo = fileProvider.GetFileInfo("/umbraco/libs/jsdiff/diff.js");
if (fileInfo != null)
{
    var path = fileInfo.PhysicalPath;
    var fileContents = System.IO.File.ReadAllText(path);
}

is working on a reply...