I really want to like VS 2015, and I really want to use it all day, and I really don't want to revert back to VS 2013 to be productive.
But there are challenges. Maybe it is because I don't understand the tool as well as I thought I did. I guess the main thing I'd like help with is to understand VS 2015 better.
Would someone please review the list of components below and provide an explanation of what they do at a high level as well as a guestimate on how they might impact the productivity of a developer during build/debug?
(Once we know what the components do at a high level, maybe we can dive into the features they support - in a separate posting. That way when one of the components seems to misbehave or consume too many resources, then we can start to disable features.
I went thru painful trial-and error to determine I needed to disable tons of stuff: Live Visual Tree, IntelliTrace, autocomplete on first character, much of the newer codelens stuff, etc.... )
Below are some components impacting productivity for build/debug (not all necessarily part of the VS 2015 distribution itself). Please help me understand them better. Maybe I missed some? I have mistrust for some of them (that have a major
presence in ProcessMonitor and ProcessExplorer) like ScriptedSandbox64.exe , Microsoft.Alm.Shared.Remoting.RemoteContainer ,StandardCollector.Service.exe
, MsMpEng.exe. Lets just say that developer productivity doesn't seem to be a fundamental goal behind all of the components below. Why would a developer tool want to be overly concerned with developer productivity anyway?
---------
ScriptedSandbox64.exe
LOCATION: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\PrivateAssemblies
PURPOSE: ????
Seems to misbehave for me and locks up the IDE regularly
---
MSBuild.exe
LOCATION: C:\Program Files (x86)\MSBuild\14.0\Bin
FREQUENCY/COUNT: Always/many
PURPOSE: devenv.exe solution dependency calculation for builds
---
VBCSCompiler.exe
LOCATION: C:\Program Files (x86)\MSBuild\14.0\Bin
PURPOSE: Roslyn? https://roslyn.codeplex.com/wikipage
SOURCE OF PERFORMANCE: Possibly!
---
Microsoft.Alm.Shared.Remoting.RemoteContainer
LOCATION: C:\Windows\Microsoft.NET\assembly\GAC_32\
PURPOSE: CodeLens?
http://www.dirkstrauss.com/visual-studio-2013-2/codelens-freezes-visual-studio#.VWcJjnlFAVP
SOURCE OF PERFORMANCE: Yes!
---
Microsoft.VsHub.Server.HttpHostx64.exe
LOCATION: C:\Program Files (x86)\Common Files\Microsoft Shared\VsHub\1.0.0.0
---
Microsoft.VsHub.Server.HttpHost.exe
LOCATION: C:\Program Files (x86)\Common Files\Microsoft Shared\VsHub\1.0.0.0
---
VsHub.exe
LOCATION: C:\Program Files (x86)\Common Files\Microsoft Shared\VsHub\1.0.0.0
---
XDesProc.exe
LOCATION: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
PURPOSE: XAML WPF designer?
---
StandardCollector.Service.exe
LOCATION: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\DiagnosticsHub\Collector
PURPOSE: Sniffing? "Insights"?
---
MsMpEng.exe
LOCATION: C:\Program Files\Microsoft Security Client
PURPOSE: Looking for viruses. Slowing things down.
---
etc....
It would be nice to have an explanation for the components now that more and more of them are exposed to us outside of devenv.exe.
David Beavon