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
Is Isolator Essential compatible yet with Visual Studio 2013? I've installed both, but the Typemock menu does not appear in VS 2013 as it did with VS 2012.
asked by lant3rn1969 (3.4k points)

19 Answers

0 votes
Hi Neil,

Thank you for the feedback.

Is faking DateTime.Now in your production code is something that you normally do?
Please try faking DateTime.Now in a context of a test and let me know if it works.

with regards to the bonus issues :|
I'm looking into it, they will be fixed in the future releases.
answered by alex (17k points)
0 votes
Hi Alex,

This code works in a test project:

[TestMethod]
public void Test()
{
   Isolate.WhenCalled(() => DateTime.Now).WillReturn(DateTime.MinValue);
}
answered by NeilJustice (14.1k points)
0 votes
Hi Neil,

Isolator is designed to work in a test project. That's why it works inside a test.
Can you describe what you're trying to do in the console application? What is the scenario you're trying to achieve by faking in a non-test process?
answered by gilz (14.5k points)
0 votes
Hi Gil,

I faked DateTime.Now in a console app as just a quick way to call Isolator to see if it worked in VS 2013. In a test project is where I would normally fake DateTime.Now.
answered by NeilJustice (14.1k points)
0 votes
Hi everyone,

New Typemock official version is waiting for you on our site.
This version supports VS 2013 along with other new features and fixes.

Your feedback will be greatly appreciated :)
answered by alex (17k points)
0 votes
Could someone help me integrate TypeMock 7.4.3 with the TFS 2013 build template, please?
TFS build server (brand new setup with the 2013 version only - not an upgrade from 2012), step TypeMockRegister fails to initialize TypeMock:

00:00:01
Source AutoDeploy location is '$/Test Builds/Solution Items'
Setting deploy directory to: C:Users<user>AppDataLocalTempBuildAgentAssemblies
Typemock AppDomain base C:Users<user>AppDataLocalTempBuildAgentAssemblies
TypeMockRegister, Company='my company', License='my license', AutoDeploy=True
Exception Message: Exception has been thrown by the target of an invocation. (type TargetInvocationException) Exception Stack Trace: at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) at System.Activator.CreateInstance(String assemblyString, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo, StackCrawlMark& stackMark) at System.Activator.CreateInstance(String assemblyName, String typeName) at System.AppDomain.CreateInstance(String assemblyName, String typeName) at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName) at System.AppDomain.CreateInstanceAndUnwrap(String assemblyName, String typeName) at TypeMock.TFS2012.BuildTasksFactory.CreateAndExecuteRegister(Dictionary`2 registerValues) at TypeMock.TFS2012.TypeMockRegister.ExecuteInternal(BuildTasksFactory tasksFactory) at TypeMock.TFS2012.TypeMockCodeActivityBase.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) Inner Exception Details: Exception Message: Could not load file or assembly 'TypeMock, Version=7.4.3.0, Culture=neutral, PublicKeyToken=3dae460033b8d8e2' or one of its dependencies. The system cannot find the file specified. (type FileNotFoundException) Exception Stack Trace: at TypeMock.Deploy.AutoDeployTypeMock.Deploy(String rootDirectory) at TypeMock.CLI.Common.TypeMockRegisterInfo.Execute() at TypeMock.CLI.Common.TypeMockRegisterInfo..ctor()


I attached my version of the build template for your reference.
TFS2012 assembly is stored in source control and Controller configured with the proper source control folder. What else I might be missing?

Thank you in advance.

MTE Template 2013.zip (Build template)
answered by dimonytch (1.2k points)
0 votes
Hi dimonytch,

We have an pre release version that support TFS 2013, you can download it from:
https://www.typemock.comilespatchesTypemockIsolatorClient7.4.3-TFS2013.msi

Please use the documentation of TFS2012: http://docs.typemock.com/Isolator/##Ref.chm/Documentation/TFS2012Build.html

The instructions are identical to TFS2013 only make sure that you use the correct files:
1. TypeMock.TFS2013.dll
2. DefaultTemplate.12.0.WithTypemock.xaml

Let me know if it helps.

P.S

The official version with this feature will be out in about two weeks time.
answered by alex (17k points)
0 votes
server returns:"File not found: /files/patches/typemockisolatorclient7.4.3-tfs2013.msi" in response to https://www.typemock.com/files/patches/typemockisolatorclient7.4.3-tfs2013.msi
answered by dimonytch (1.2k points)
0 votes
Hi,

Sorry, my bad :oops:
Use this instead.
answered by alex (17k points)
...