I am trying to profile Visual Studio 2019 to import registry and file settings to UEM. I run Application Profiler, select VS2019. It runs, i start without code and then close the app. But profiling doesn't stop. So i click Stop Analysis button and it says that one process is still running. ServiceHub.SettingsHost.exe (or IdentityHost). Can't find this process anywhere by its name or PID. Maybe with 2019 it is part of some service? Or maybe it is not actually running and Application Profiler is "thinking" it is still on, a glitch?
Accepted Solutions
Hi olegkz,
That's most probably due to the Exclusions that are configured by default. When you profile an application, Windows itself will access all kinds of Microsoft registry keys and files, which typically should not be included in the generated Flex config file for that particular application.
For that reason, Application Profiler excludes those paths by default, but that can cause the symptoms you're describing when you're trying to profile a Microsoft application that actually saves its settings in those locations...
As a quick test, you can un-check the two exclusion options:
That will probably result in a lot of irrelevant locations to be captured. For a more targeted approach, you can modify the specific exclusions via the two Manage Exclusions buttons:
Just to make sure, the templates repository contains a template for Microsoft Visual Studio:
Does that not work (sufficiently well) for Visual Studio 2019?
Hi olegkz,
It can occasionally happen that Application Profiler doesn't notice that a child process has terminated, which is exactly why we have that dialog 
.
Given that you don't see the process running any more, it may have exited slightly later than the main executable. "ServiceHub.IdentityHost.exe" does not sound like a particularly relevant process, so probably Application Profiler won't miss any important profile settings.
Hi olegkz,
That's most probably due to the Exclusions that are configured by default. When you profile an application, Windows itself will access all kinds of Microsoft registry keys and files, which typically should not be included in the generated Flex config file for that particular application.
For that reason, Application Profiler excludes those paths by default, but that can cause the symptoms you're describing when you're trying to profile a Microsoft application that actually saves its settings in those locations...
As a quick test, you can un-check the two exclusion options:
That will probably result in a lot of irrelevant locations to be captured. For a more targeted approach, you can modify the specific exclusions via the two Manage Exclusions buttons:
Just to make sure, the templates repository contains a template for Microsoft Visual Studio:
Does that not work (sufficiently well) for Visual Studio 2019?
