MSBee & TestDriven.Net

Topics: For MSBee Developers
Aug 16, 2006 at 6:34 AM
migrated from power toy forums
originally posted by Jamie Cansdale
------------------------------------------------------

This is something I'm considering adding to TestDriven.NET (in order to support 'Test With... .NET 1.x'). I'm already using MSBuild to detect VS2005 'Team Test' project types. It wouldn't be a huge stretch to add conversion to and from regular (non 'Team Test') project types. If I'm doing this I would also like to add support for MSBee.

Let me know if you think this functionality would be useful.

Thanks, Jamie.
http://www.testdriven.net/
http://weblogs.asp.net/nunitaddin/
Aug 16, 2006 at 6:34 AM
originally posted by Craig Lichtenstein - MSFT
------------------------------------------------------

I'm not quite clear on what you're proposing. Are you asking about converting the test projects, that TestDriven.NET creates, to target .NET 1.1 so the user can test their app when its built against .NET 1.1? Or, are you asking about building a regular C# or VB project using MSBee as a test for .NET 1.1 compatibility? Or, something else?

-Craig
Aug 16, 2006 at 6:34 AM
originally posted by Jamie Cansdale
------------------------------------------------------
Hi Craig,

I'm suggesting building (and testing) a regular C# or VB project using MSBee as a way of ensuring .NET 1.1 compatibility. At the moment when TestDriven.NET does a test run, it first compiles using the default Visual Studio compiler. If I wanted to do a test run using a .NET 1.1 process, I would need some way to compile targeting .NET 1.1. I'm thinking I could detect MSBee and persuade Visual Studio to compile using that.

Thanks, Jamie.
http://www.testdriven.net/
http://weblogs.asp.net/nunitaddin/
Aug 16, 2006 at 6:34 AM
originally posted by Craig Lichtenstein - MSFT
------------------------------------------------------
That sounds like a very neat idea. Since MSBee can only be triggered from the command line, you can try creating a Process object that runs msbuild.exe with the TargetFX1_1 property set to true on its command line. The return code from msbuild.exe should indicate whether the build was successful and you could redirect the MSBuild output to a test results window. I already do something like this for performing automated tests of building VS projects with MSBee.

If you have additional questions, let me know.

-Craig