Would it be recommended to write Test in C# and production code in vb.net

After some hours creating a vb.net helper class for unit-tests and integrating moq into the project followed by a smashing hit on the "Run tests" Key-Command and then a Red Light revealed himself.

To save you the trouble of what happened. The answer that explained the problem can be found here : Experiences using moq with VB.Net

So i tough hey lets just write the test in C# ! (type mock is not an option)

After 15 min a shiny green light while the vb.net test still fails.

Would it be recommended to continue writing test in C# with a mocking framework. Or just implement for each Real-Interface a Fake-Interface in vb.net

Some constraints on the freedom are :

• production code must be in visual basic
• They don't know what TDD is so i shouldn't be writing test but then again thats like putting yourself ready to fall into the debug-nightmare cliff again.

Or is there 开发者_StackOverflow中文版an alternative approach to this?

Also my apologizes for my not so great English writing style (I am working on it)

As soon as your VB.NET code is CLSCompliant you shouldn't run into any problems. But if you are using some VB.NET specific features such as Optional then it might get awkward.

r just implement for each Real-Interface a Fake-Interface in vb.net

Don't to that, it's just waste of time.