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
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
In trying to run tests in my builds I'm getting the exception below. This is a new purchase for us, so any assistance is greatly appreciated.

Unit Test Adapter threw exception: 
Type is not resolved for member 'TypeMock.TypeMockException,TypeMock, Version=7.0.6.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2'..

I followed the online guidance.

My build account is in the Administrators group and has full permission to modify the following registry keys (these were the only two that seemed to produced an issue):
HKEY_LOCAL_MACHINESOFTWAREWOW6432Node
HKEY_LOCAL_MACHINESOFTWARETypeMock


I updated the build definition to ensure it was building x86 (as that's the version of MockWeaver and ProfileLinker that are in custom assemblies... see below).
I update the build configuration to ensure the test projects were being built (though their target platform is still "Any CPU")

Here's my CustomAssemblies folder:
http://screencast.com/t/OTwhMwuSeZ

This is what my template looks like:
http://screencast.com/t/D3ihDOdRpQq

Here's what the diagnostic log file shows (I added the <SNIP>'s to hide sensitive info):
TypeMockRegister
Initial Property Values
AutoDeploy = True
Company = <SNIP>
License = <SNIP>
Typemock Isolator Auto Deployed, version 7.0.6.0
Final Property Values
AutoDeploy = True
Company = <SNIP>
License = <SNIP>

00:00
TypeMockStart
Initial Property Values
EvaluationFolder = 
Link = 
LogLevel = 
LogPath = 
ProfilerLaunchedFirst = False
Target = 
Final Property Values
EvaluationFolder = 
Link = 
LogLevel = 
LogPath = 
ProfilerLaunchedFirst = False
Target = 
Version = 7.0.6.0

00:39
If Not TestSpecs Is Nothing
Initial Property Values
Condition = True
<SNIP>


I'm happy to provide any additional information.
asked by stealthsid (720 points)

7 Answers

0 votes
Hi,

We are trying to recreate the case, I will return to you within the next week.

Regards,
Alex, Typemock Support.
answered by alex (18k points)
0 votes
Hi,

We have recreated the case. I will contact you with a solution for this issue later this week.

Regards,
Alex,
Typemock Support.
answered by alex (18k points)
0 votes
How are things looking?
answered by stealthsid (720 points)
0 votes
Hi,

We've made some progress and are still working on it.
Have you got the workaround that I sent to your email?
answered by alex (18k points)
0 votes
Hi,

We changed the way Isolator integrates with TFS, it's much more simple now.
It's available from version 7.0.8, also there are new instructions in the docs.
If you need any help please contact us.
answered by NofarC (4k points)
0 votes
Thanks for your replies. I'm sorry I hadn't responded and I appreciate your effort, but I was pulled away from this effort. I'll try the new version and report my success or failure here.
answered by stealthsid (720 points)
0 votes
I did run into one additional problem which I was able to overcome on my own. After the update I was getting the following error:

*** Typemock Isolator Cannot be deployed, following file is required: C:UsersTFSBuildAppDataLocalTempBuildAgent
amespaces.dat C:UsersTFSBuildAppDataLocalTempBuildAgent	ypemockconfig.xml C:UsersTFSBuildAppDataLocalTempBuildAgentexclude.dat C:UsersTFSBuildAppDataLocalTempBuildAgentlacklist.dat C:UsersTFSBuildAppDataLocalTempBuildAgentMockWeaver.dll C:UsersTFSBuildAppDataLocalTempBuildAgentProfileLinker.dll


I noticed that the similar folder location for the BuildController contained these files, but the folder for the BuildAgent did not. I copied from the BuildController folder to the BuildAgent folder, and all was well.

Thanks for your help.
answered by stealthsid (720 points)
...