Profiling .NET 7 assemblies now supported

Comments

• CodingDutch Posts: 7 Bronze 2

  October 3, 2023 10:19AM edited October 3, 2023 11:58AM

  I noticed the new documentation does not describe Memory Profiling an 'IIS Express - ASP.NET Core' application. The GUI expects a path to a configuration file, which is not described. I first had no idea what config file is needed here, but I later found out it is 'applicationhost.config'. Unfortunately, out of the box it points to a wrong directory (somewhere in my documents). I did a search and found the file on 'C:\Program Files\IIS Express\AppServer'. The problem, it gives a 'no asp.net core websites are found' exclamation mark is shown next to the path.
  
  After further investigation, I noticed I should point the path to (maybe because I use JetBrains Rider):
  
  C:\<my source folder>\.idea\config
  
  If you are using Visual Studio it probably needs to point to: C:\<my source folder>\.vs\config
  
  Unfortunately, it does not work because I get an http error related to the application cannot find the correct connection string to my local SQL Server instance.
  I noticed I needed to set 2 environment variables to make it work:
  
  1. ASPNETCORE_CONTENTROOT Which must point to the root folder of where the Web API dll resides. So if the 'ASP.NET Core assembly' path points to 'C:<your source folder\<your api>\bin\Debug\net7.0\YOUR.API.dll', the value is 'C:<your source folder\<your api>'
  2. ASPNETCORE_ENVIRONMENT with value 'Development'
  
  
  

  1 · Share on Twitter
• Peter_Laws Redgate › Posts: 272 Silver 2

  October 5, 2023 4:00PM

  Thank you for your investigation CodingDutch, I'll feed this back to our development team.

  Kind regards

  Peter Laws | Redgate Software

  Have you visited our Help Center?

  0 · Share on Twitter