Severe performance penalty after upgrade to 4.1

Additionally, when launching TypeMock configuration from Visual Studio we now get the following error:

---------------------------
TypeMock Problem
---------------------------
Please send the following error to TypeMock Support:The system cannot find the file specified    at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)

   at System.Diagnostics.Process.Start()

   at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)

   at TypeMock.AddIn2005.Connect.a(String A_0)
---------------------------
OK   
---------------------------

The configuration is still accessible via Start > Program Files, so there's an easy workaround, but I might as well mention it.

Brian hi,

reagrding the perofmance hit. Its not something we have encountered so far. It will require further investigation so i suggest we take it offline. I'll send you an email regarding this.

About the add-in, sometime it happens due to installation problems. I'm guessing that it started to happen only after the roll back to 4.0.1.

In any case what I suggest is to reinstall TypeMock while making sure that all instances of visual studio are closed. This should fix the add-in problem.

If it doesnt please let me know (and also specify which visual studio you are using).

Hi,

I look forward to hearing from you then :). We have had no problems with performance either prior to this, so it came as a big surprise.

Regarding the add-in we have already tried to uninstall and reinstall to no avail. Is there a registry setting or similar that I should delete as well?

Thanks,
Brian

It usually happen if during the install an instance of VS is open.
in any case if you are working on VS2005 you need to make sure that the following files:

TypeMock.AddIn2005.AddIn
TypeMock.AddIn2005.dll

are in the VS add-in folder:

$(CommonAppDataFolder)/Microsoft/VisualStudio/8.0/AddIns

on vista for example this translate to:

C:ProgramDataMicrosoftVisualStudio8.0Addins

Also check the values in the registery under

HKEY_CLASSES_ROOTCLSID{E1A6A8C8-C7FA-4F97-843F-83F638EA4248}InprocServer32

and verify it points to TypeMock installation directory. (C:Program FilesTypeMockTypeMock.NET)

:!: if youre working on 64 bit machine registery and paths changes.

Hi
We also upgraded from 4.0.1 to 4.1.0 and measured a big performance degradation of our test suite. Our test execution time went from 15 minutes to 35 minutes.

We downgraded now to 4.0.1.

Please investigate in this issue as we want to use the new features of typemock 4.1.0.

Thanks,
Marco

Hi,
we're also suffering a big performance hit due the upgrade. We've passed from about 80 seconds (TypeMock 3.7.1) to more than 233 seconds (TypeMock 4.1.0).

Please let us know something about this issue.

Thanks,
Andrea

Just a little update about performance hit: with TypeMock 4.0.3, all the tests run in about 177 seconds.

I would like to stress the fact that, since we've adopted TDD methodology, it's vital for us to be able to run all tests very fast, since we run them very often.

Hi
Can you please send us the tests code?
I will send my address offline.

I ran our 1,891 tests. The run on 4.0.3 takes 9 minutes. The run on 4.1.0 takes 56 minutes.

Hi,
The problem that caused the perfomance penalty was probably found.
We are currently in the final steps of verifying this.
the fix will be released in our next version.
If anyone here would like we can send him the patch for this.
just let us know if you would like to try it out.