I'm guessing that there are issues with having multiple System, mscorlib, etc. Libraries in the app domain that probably confuse the test execution environment.
I'm guessing that there are issues with having multiple System, mscorlib, etc. Libraries in the app domain that probably confuse the test execution environment. Can you separate this into multiple test runs for the TFS build, OR perhaps author an msbuild script with code to call mstest. Exe for one of them and get results that way?
Thanks Jeff, we solved it by calling mstest. Exe in our build script twice (once for . NET tests, once for Silverlight tests).
– Phil Dec 23 '09 at 22:15.
They can both be triggered the same way or at the same time. The only difference is that you have references to just the SL projects in one and just the . NET projects in another.
If you didn't want to reference the projects from the build definition you could create a couple of solutions to use with your builds and reference only the SL projects in one solution and just the . Net projects in another.
You can also use a Silverlight Test Project (created from the Silverlight Toolkit project template) and use this solution to run your Silverlight test on your TFS build server.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.