Question

I have a standard WPF application.
The VS solution has a main project and a unit test project (using the standard VS unit test suite)

For testing purposes beyond unit tests (e.g. just interactively trying out a new piece of code) I have to wait for my whole application to start and then click my way to the form I want to test.

I’d prefer if I could choose an alternative build with a different entry point, which skips all the stuff I do not need and drops me off right where I want to.
I have created an additional build configuration besides “debug” and “release” called “debug (test)”.
How do I set different startup object that is executed when I choose this build?

Or is there an alternative solution for this problem? To simplify testing and profiling I’d prefer something that does not involve adding an additional project or dll.

One possible solution would be to define a compiler symbol and check for it in my app.xaml.cs

#if DEBUG_TEST
    TestWindow view = new TestWindow();
    view.Show();
#else
    MainWindow view = new MainWindow();
    view.Show();
#endif

anything less hacky?

Answer 1

I don’t know why you consider this approach ‘hacky’.
This seems to be the right way to go.
Just select your configuration DEBUG(TEST) and add the DEBUG_TEST define to the properties page of your project.

Return to normal configuration when you have done with your tests.