Specifically, those dependencies aren't broken - they're
intercepted. It's not entirely disingenuous to say that
dependencies are broken, but the "break dependencies"
terminology colloquially refers to a design activity
rather than such a brute force countermeasure.
Wow, very timely. I have a spike to work on just this
very item. Thanks.
Looks like Visual Studio has a bit of a issue with the
code coverage feature and Silverlight applications. The
test run config dialog disappears when you click on the
code coverage list item.
Chandra :
that is because the NUNIT gui was not running with
Typemock Isolator enabled on it's process.
either run "TmockRunner.exe nunitgui.exe" which will
enable this, or start Nunit from within visual studio
(if you have testdriven .net you can right click on the
test project and select test with->nunit"
It did not solve the issue.
Now, I also commented the typemock code and tried to run
NUnit from visual studio as well.
It throws the same exception.
Invalid Cross Thread access.
I think the Nunit is running on different thread from
Silverlight UI. So, it is complaining. Do I need to add
any configuration file into my silverlight project so
that Nunit tests will have access to silverlight thread?
--Chandra
Roy sent me the CThru that was built with TypeMock5.2.3.
When I used this CThru 5.2.3 alogn with TypeMock5.2.3,
it has resolved the CrossThread access issue. Now, the
silverlight calls are being intercepted successfully
when UnitTests were executed.
Thanks to Roy. I apprecieate your help.
I hope it would help somebody else too who might face
this issue.