Intallation observations

Hi there,
I'd just like to make some observations (NOT critisisms!) about my installation experience for TypeMock.net - maybe it will help make a great product better...

1) My dev box is a 64bit machine, my build server is 32 bit. When installing on a 64bit machine, TypeMock wants to install into "Program Files (x86)", and on a 32bit machine it wants to install into "Program Files".

When I add an assembly reference to the TypeMock.dll, on my dev box, it references the TypeMock DLL in the x86 folder, but this breaks the build on the build server, as it cannot find the DLL.

I tried to change the installation dir on the 64bit machine to be "Program Files", but the dialog would not let this happen.

To get over this issue, I needed to add a "Lib" folder to my Team project, copy the DLL into that folder and reference that DLL. So that when the build server pulls the source and lib folders from TeamSystem, it will find the referenced DLL.

2) I modified my TFSBuild.proj to use the <TypeMockStart> and <TypeMockStop> tasks as recommended in the documentation, however it neglected to mention that the TypeMock.MSBuild.tasks needs to be imported into the TFSBuild.proj file.

However, the .tasks file is in the TypeMock installation folder, which due to issue 1 above, poses problems for 64bit vs 32bit machines. The standard approach for task definition files is to install and reference them from the $(MSBuildExtensionsPath) folder, which is (from the POV of the .proj file) platform independent. IF this was the case, then the following could be added:

<Import>

But this is not the case.

To get over this issue, I needed to add both the TypeMock.Msbuild.DLL and TypeMock.MSBuild.tasks to my TeamBuildTypesuildtype folder. I was then able to add the following to my TFSBuild.proj file:

   <Import>
   <Target>
      <TypeMockStart>
   </Target>
   <Target>
      <TypeMockStop>
   </Target>

Anyway, these are minor issues to overcome compared to the benefits that TypeMock is brining to my testing.

Sincerely
Pete
________
Vaporizer forums