This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(22.400000000000002, 25%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Hi,
After updating several Nuget packages in my application I get assembly loading errors that I wanted to debug using the Fusion logs.
For some reason the loading errors dose not occur when running on my dev machine, but only when running in the Azure Cloud service (classic).
In order to debug the assembly loading errors in the Azure instance, I remoted into the instance and did the registry edits to enable Fusion logs.
Logs start showing up for other application, but not the ASP.Net app.
Is there some other way to access the Fusion logs when running in Azure or perhaps a totally different way to debug assembly loading errors?
Kind regards
Anders Bergvit
Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.
I have reached out to internal team on this, will update back here.
It might be an issue with the IIS worker process (w3wp.exe) account (network service) not having permissions to write to the fusion logs folder.
This document has instructions to enable fusion logging but you probably already have done this, just need to make sure the permissions are configured on the folder.