Using Magick.NET on Azure

[isonil]

Hi,

does anyone know if it's possible to use Magic.NET in an ASP.NET application deployed to Azure? I have added these 2 NuGet packages:

• Magick.NET.Core
• Magick.NET-Q8-AnyCPU

This seems to work fine locally. However, it fails while deploying to Azure App Service. It takes a very long time to deploy and then fails with the following message:

Command 'starter.cmd "C:\home\site\d ...' was aborted due to no output nor CPU activity for 300 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd "C:\home\site\deployments\tools\deploy.cmd"
_CopyFilesMarkedCopyLocal:
One or more errors occurred.
Command 'starter.cmd "C:\home\site\d ...' was aborted due to no output nor CPU activity for 300 seconds. You can increase the SCM_COMMAND_IDLE_TIMEOUT app setting (or WEBJOBS_IDLE_TIMEOUT if this is a WebJob) if needed.\r\nstarter.cmd "C:\home\site\deployments\tools\deploy.cmd"

Thanks in advance,
Piotr

[dlemstra]

You can probably get more details in the event viewer of that app service. Have you tried searching the logging?

[dlemstra]

Thanks will try to take a look at it once my MSDN license issues have been resolved. Not sure when that will happen though.

[isonil]

Great, thanks.

[dlemstra]

I was able to publish your project to Azure without any issues with the free service plan "(F1: Free)". Maybe you got firewall issues where VisualStudio is not allowed to push the files to Azure?

[isonil]

Huh, interesting, thanks for checking! If it actually worked and you could see the default home page then perhaps it's something on my end then. I'm using continuous deployment with Bitbucket. Maybe my app service is just too bloated and there's not enough space or something.

[dlemstra]

I saw the default home page. Not sure what is happening on your end.