I have a bunch of unit tests written in C# that use moles for mocking a serial port class. I'm using Visual Studio 2008. This has all worked fine until today when I went to re-run the tests... and as soon as it tries to create an MSerialPort object, the warning box pops up with the message "Microsoft.Moles.VsHost has stopped working". I've tried re installing moles, etc but not sure what else to try or where to find more information on this. None of the tests themselves have changed so it's got to be something with the .net runtime or the like. I'm using .net 3.5. Anyone else run into something like this?
相关问题
- Microsoft Moles HostType errors in TFS 2010 Lab Ma
- Moling DataContext with MS Moles?
- Am I the only one getting “Assembly Not Available
- .NET Moles Stub Fallthrough Behaviour
- mocking session variable in unit test using Moles
相关文章
- Moling DataContext with MS Moles?
- Am I the only one getting “Assembly Not Available
- .NET Moles Stub Fallthrough Behaviour
- mocking session variable in unit test using Moles
- VS2010亲无法启动主机痣(VS2010 pro not able to start Moles
- Microsoft.Moles.vshost已停止工作(Microsoft.Moles.vshost
- How to use mole manually in Visual Studio Express?
- 垫片不是.NET方法产生(Shims are not generated for .NET meth
Found the problem... something about security update KB2742599 (security update to .NET 3.5) broke moles. I uninstalled this update, restarted the PC, and everything works fine again. I'm using windows 7 SP1, x86.