Are you sure all the related files are there too, config files etc?
You could try to restart the environment (from the UaaS portal).
And of course it's always good to check the logs for errors.
The other thing I do if I want a really rough look at what's going on is go into Kudu and hit download on wwwroot in the debug console.. then I just do a BeyondCompare to see what's different between local and remote to see if I did something silly.
Thank for the tips Seb, yeah we did a compare but the strange thing is when we now clone the site the dll isn't there (the ImageProcessor.Web.Plugins.AzureBlobCache one) so we added that and did a push that currently fixes the problem (so the site is running now) but still super strange that the file would show in kudu.... and not when cloning...
Weird! Was it showing in wwwroot or in repository? Could be that there was a problem deploying from repository to wwwroot so it didn't get copied to the actual site.
I found this thread because I encountered a similar issue, so I'm replying in case anyone else finds the same.
I am moving an Umbraco site from dedicated hosting to Azure web app hosting. This involves installing ImageProcessor Azure Blob Cache. After installing via nuget and setting up the configs, the site built but produced this runtime error.
The fix was to upgrade the .NET version (from 4.5.1 in my case) to the required 4.5.2. And also to upgrade the existing ImageProcessor nuget packages to the latest version. The version dependencies are listed on the nuget packages, but weren't enforced on my build machine - leading to missing dlls.
Topic author was deleted
Couldn't load IImageCache
Hey,
We just deployed an existing web app to Umbraco Cloud but getting the error now
Couldn't load IImageCache: ImageProcessor.Web.Plugins.AzureBlobCache.AzureBlobCache, ImageProcessor.Web.Plugins.AzureBlobCache
Assembly is in the bin dir... so not sure why it can't find the type
Anyone have a clue?
Are you sure all the related files are there too, config files etc?
You could try to restart the environment (from the UaaS portal).
And of course it's always good to check the logs for errors.
The other thing I do if I want a really rough look at what's going on is go into Kudu and hit download on wwwroot in the debug console.. then I just do a BeyondCompare to see what's different between local and remote to see if I did something silly.
Comment author was deleted
Thank for the tips Seb, yeah we did a compare but the strange thing is when we now clone the site the dll isn't there (the ImageProcessor.Web.Plugins.AzureBlobCache one) so we added that and did a push that currently fixes the problem (so the site is running now) but still super strange that the file would show in kudu.... and not when cloning...
Weird! Was it showing in
wwwroot
or inrepository
? Could be that there was a problem deploying fromrepository
towwwroot
so it didn't get copied to the actual site.Comment author was deleted
Was showing in wwwroot so yeah that's super strange
I'm having the exact same issue. What is the filename of the DLL that you were adding ?
Comment author was deleted
think it was ImageProcessor.Web.Plugins.AzureBlobCache.dll
That is weird.
That file is not a part of the package. Could you in any way send it to me ?
Maybe a link in this thread ?
Really weird. That file is not a part of the package.
Could you in some way send me the file through a link or something ?
Comment author was deleted
Sure you can get it here https://www.nuget.org/packages/ImageProcessor.Web.Plugins.AzureBlobCache/ (you can download nuget, name to .zip en extract)
I found this thread because I encountered a similar issue, so I'm replying in case anyone else finds the same.
I am moving an Umbraco site from dedicated hosting to Azure web app hosting. This involves installing ImageProcessor Azure Blob Cache. After installing via nuget and setting up the configs, the site built but produced this runtime error.
The fix was to upgrade the .NET version (from 4.5.1 in my case) to the required 4.5.2. And also to upgrade the existing ImageProcessor nuget packages to the latest version. The version dependencies are listed on the nuget packages, but weren't enforced on my build machine - leading to missing dlls.
Hope this helps.
is working on a reply...