Sorry to answer only now, I was out of the office with limited access to my mails.
The most simple way to do that is to have in the same workspace your “normal” application project, taht contains all the source code you need, plus one UnitText_xxx project for each unit test. In each UnitTest rpoject you may then link to the appropriate source code from your application project so that they are recompiled in the unit test project, while the source code is not duplicated.
If you have a quite complex test harness that is common (at source level) to all your unit test projects, you could create a “main” unit test project with the code for the test harness, in a ‘’TestHarness’ directory, a simple main file that invoke your unit tests using this test harness and a dummy unit to test.
Then for each new test you can just create a new project, reference the TestHarness directory in this project (using a link), link also the source code for the unit to test then create the main program to create and pass the unit tests. As long as the links you create a workspace links, it should work flawlessly.
If you create a dummy unit test (that includes a link to the TestHarness) then this project can be copied and pasted to create all the unit test projects where you only have to link the unit to test source code and create/pass the tests in the main (pass and analyze phases can be generic in fact...) A nice feature is that if the project you copy has a name that ends with a number, the paste will automatically propose as name the sae name, but with the final counter incremented...