chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
0 votes
With TypeMock Isolator on, the CLR profiler hurts our performance significantly. That is not a problem since we can disable it - but the disable does not take effect immediately.

To get performance back, I must click "Tools - Disable TypeMock Isolator" then run the application, then exit the application. Subsequent runs are fast again.

The same thing happens with enable: I select "Tools - Enable TypeMock Isolator" then I must run the application before I see the performance degradation.

I suspect this is a bug in the IDE integration.
asked by MobyDisk (3.6k points)

11 Answers

0 votes
CLR Profiler loads when the process starts so if your test framework or application already loaded/running the changes (diable/enable) won't be applied until you restart the application or test framework.

Just to clarify by Application I mean the currently debugged code not Visual Studio.

What kind of application are you running?
answered by dhelper (11.9k points)
0 votes
"CLR Profiler loads when the process starts "

Aha! That lead me to discover the cause: Project - Properties - "Enable the Visual Studio hosting process" (This is happening on a WPF application, but I assume it will happen on anything.)

If I uncheck that box, then the change takes effect immediately.

Ideally, I would want it enabled only when running a unit test. Is that possible?
answered by MobyDisk (3.6k points)
0 votes
All you need to do is to close the running application so that the changes take effect. I'm not sure about WPF but in most vs project that step was not needed
answered by dhelper (11.9k points)
0 votes
The application is not running when this happens. I also noticed two other things:

1) Visual Studio does not remember the setting. If I disable typemock, then exit Visual Studio, then run Visual Studio again - typemock is enabled.
2) On a coworker's computer, Typemock prompts the user when you toggle this setting. The prompt asks if TypeMock should automatically end the visual studio hosting process. This message does not appear on my box.
answered by MobyDisk (3.6k points)
0 votes
it will only ask the user about closing processes if they are indeed detected.
it looks for, among others "vstesthost.exe"

it either does not find it, or you are using an older version of isolator that does not contain this feature.

which version do you have installed?

what VS version are you using?

can you verify you are running devenv.exe with admin privileges?
answered by royo (2k points)
0 votes
Visual Studio 2008 SP 1
TypemockIsolatorSetup531.msi

The visual studio hosting process is running right now, and it is named ProjectName.vshost.exe.

---- More detail that you ever wanted to know, follows... ----

Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
Version 3.5 SP1

Installed Edition: Professional

Microsoft Visual Basic 2008 91605-270-2978547-60010
Microsoft Visual Basic 2008

Microsoft Visual C# 2008 91605-270-2978547-60010
Microsoft Visual C# 2008

Microsoft Visual C++ 2008 91605-270-2978547-60010
Microsoft Visual C++ 2008

Microsoft Visual Studio 2008 Tools for Office 91605-270-2978547-60010
Microsoft Visual Studio 2008 Tools for Office

Microsoft Visual Web Developer 2008 91605-270-2978547-60010
Microsoft Visual Web Developer 2008

Crystal Reports AAJ60-G0MSA4K-68000CF
Crystal Reports Basic for Visual Studio 2008


Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB944899) KB944899
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/944899.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB945282) KB945282
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/945282.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946040) KB946040
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/946040.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946308) KB946308
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/946308.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946344) KB946344
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/946344.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB946581) KB946581
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/946581.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947171) KB947171
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/947171.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947173) KB947173
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/947173.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947180) KB947180
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/947180.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947540) KB947540
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/947540.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB947789) KB947789
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/947789.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB948127) KB948127
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/948127.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB952241) KB952241
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/952241.

Hotfix for Microsoft Visual Studio 2008 Professional Edition - ENU (KB953256) KB953256
This hotfix is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/953256.

Microsoft Visual Studio 2008 Professional Edition - ENU Service Pack 1 (KB945140) KB945140
This service pack is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/945140.

Microsoft Visual Studio 2008 Professional Edition - ENU Service Pack 1 (KB947888) KB947888
This service pack is for Microsoft Visual Studio 2008 Professional Edition - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/947888.

Mic
answered by MobyDisk (3.6k points)
0 votes
Is your application running when you disable Isolator?
answered by dhelper (11.9k points)
0 votes
No, the application is not running.

Let me clarify the situation:
I have a solution which contains various library projects, several unit test projects, and one single executable application project I'll call "MyApplication". The "Enable the Visual Studio hosting process" box is checked on the executable application project.

As soon as I open the solution file, Visual Studio automatically runs "MyApplication.vshost.exe" and I believe it attaches the CLR profiler to that EXE. At this point, my answer to your question is "No, the application is not running."

However, I believe that this point is causing the confusion. From the developer's point of view, I am not running the application. But from Visual Studio's standpoint, the host is running and the CLR profiler is attached. So for "Disable TypeMock Isolator" to work, "MyApplication.vshost.exe" must be restarted.

Does this clarify things? I think, to make this menu option take effect immediately, the add-in needs to find the MyApplication.vshost.exe and restart it.
answered by MobyDisk (3.6k points)
0 votes
Hi,

Thanks for the clarification.

In order to restart Isolator the process must be restarted. When disabling Typemock Isolator it looks for test runners and terminates them.

Since your application starts out of test runner context you have to restart it in order to make it run with disabled Isolator.

Best Regards,
Elisha
Typemock Support Forum
answered by Elisha (12k points)
0 votes
Is there a registry key to disable TypeMock by default? So long as TypeMock is installed, I really can't do "normal" development without extra steps.

Every time I open Visual Studio, TypeMock reverts back to "Enable TypeMock Isolator." So I must disable it, then run my program twice. Only after that am I able to get back to running and debugging an application normally. And if I exit Visual Studio, or if it crashes, I have to do it all over again. Since I am working on software with a significant startup time, and since the CLR profiler really really slows down the app, I spend several minutes getting things back to a state where I can run and debug again.

TypeMock should default to disabled, and should only enable when running a unit test. Most of my time is not spent working on unit tests (well, not yet) so defaulting this to "enabled" is counter-productive.
answered by MobyDisk (3.6k points)
...