none
.Net Profiler - Azure App Service defining helper assembly RRS feed

  • Question

  • I am trying to deploy my .Net instrumentation profiler into Azure's App Service. I have added my profiler dlls in my visual studio solution and published into the app service.

    The COR_* profiler environment variables are set to the w3wp.exe while it gets started using applicationHost.xdt file. Since the environmental variable is set my profiler dll is getting loaded by the w3wp.exe.

    During JIT compilation and when i inject my code and modify the functions body, my injected lines of code calls the helper functions that are defined in the C# helper assembly which will be present in GAC of the machine.

    The issue is here .. The injected code is breaking and causing the application to fail loading, since it cannot find the definition of the function called(the helper assembly is not loaded). I cannot add the helper assembly using GACUTIL in the App Service too. Now how can i define the helper assembly for my injected code to get executed.?

    Is there something else needs to be done to define the separate C# helper assembly that has the definition of the injected function calls.???


    Friday, May 4, 2018 7:29 AM

All replies

  • Hi Selva VS,

    Thank you for posting here.

    For your question is more related to Azure, Please post a new thread in Azure App Service - Web Apps forum for suitable support.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions.

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, May 7, 2018 1:04 AM