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
Hello,

I had a VB project build with Typemock 6.0.3 referenced, compiled and all tests where green.

I ran the 6.0.4 installer, and the project does not compile anymore.

The references for the test project refer to the new 6.04 dll's but the errors/warnings are:


Warning   1   Could not resolve this reference. Could not locate the assembly "Typemock.Isolator.VisualBasic, Version=6.0.3.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.   DCDC_Poort_VB_Tests

Warning   2   Could not resolve this reference. Could not locate the assembly "TypeMock, Version=6.0.3.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.   DCDC_Poort_VB_Tests

Warning   3   Namespace or type specified in the Imports 'TypeMock.Isolator.VisualBasic' doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliases.   C:DevelopmentTestDCTestForm1DCDC_Poort_VB_TestsKCFactorysTests.vb   4   9   DCDC_Poort_VB_Tests



Do I have to remove and add the references for TypeMock in each project when an update for Isolator is installed? (this solves the problem)

Are there breaking changes that necessitate this remove and re-add of typeMock to the project?

Can the reference be made version independent?


Regards,
Ed

ps my dev environment is VS2008
asked by Ed (1.1k points)

2 Answers

0 votes
Hi Ed,

There are no breaking changes between the versions.
Version 6.0.4 is mostly bug fixes.

To solve this try to set the "Specific version" property of the assemblies to false.
To do that right click on the assembly in Visual Studio and choose "Properties"
In the properties window change the "Specific version" from true to false.

Please let me know if it helps.
answered by ohad (35.4k points)
0 votes
Hi Ohad,

Thanks!
This solved the problem.
In future test projects when adding the references to TypeMock, I will change their "Specific Version" property in the project to false.

(It might be an idea to mention this somewhere in the quick-start)

Regards,
Ed
answered by Ed (1.1k points)
...