<system.diagnostics>

Discussion in 'ASP.NET / ASP.NET Core' started by gavin, Nov 8, 2018.

  1. I have a <system.diagnostics> section in a web.config for an ASP.NET web application that's deployed under our web site's main application.
    Diagnostics are configured to write to a file in the logs folder underneath the application's root folder.
    The application works fine except no diagnostics are written to the log file.
    Diagnostics work as expected when deployed to my localhost IIS.
    However, when I deploy the exact same compiled and published application to DASP, nothing is written to the log file and no errors are thrown etc.
    Are there any tricks to get diagnostics working on DASP?
    Thanks.
     
  2. RayH

    RayH DiscountASP.NET Lackey DiscountASP.NET Staff

    What's the path to the log file? Are you using absolute or relative pathing?
     
  3. Hi Ray
    My apologies. It was actually working. I just didn't realize.
    It was a long day yesterday!
     
    martino and RayH like this.

Share This Page