Use this forum for questions on how to use .NET Memory Profiler and how to analyse memory usage.
- Posts: 2
- Joined: Wed Mar 19, 2014 1:56 am
We've developed a 64-bit service that will be deployed into IIS. We are developing it using VS 2015 and using IIS Express on the desktop. When we try to profile it, it doesn't appear in the list of IIS Express sites. Based on http://stackoverflow.com/a/12946477
it looks like .Net Memory Profiler is taking the old config file, and is not aware of the new VS2015 config location.
As a workaround, I thought I'd start IIS Express from VS2015 and then attach the profiler to the running iisexpress.exe, but this process does not show up in the list of .Net processes.
Please let me know how I can profile my service.
FYI I'm using Win7 x64 Service Pack 1, VS 2015 update 3 and Memory Profiler 220.127.116.11.
- Posts: 1029
- Joined: Wed Mar 02, 2005 7:53 pm
You are correct, .NET Memory Profiler only uses the default IIS Express config file. It should definitely use the one created by Visual Studio 2015 instead. We will soon release a maintenance release of version 5.0, and will include a fix for this issue.
In version 5.5 we will also include the possibility to select which configuration file to use in the user interface (when selecting Profile ASP.NET and IIS Express).
SciTech Software AB
Users browsing this forum: Google [Bot] and 21 guests