On Thu, Jun 26, 2008 at 6:56 PM, Wendy Smoak <
wsmoak@...> wrote:
> On Thu, Jun 26, 2008 at 1:01 AM, Jan Stevens Ancajas <
jancajas@...>
> wrote:
>
> > It should be the JavaBinding that generates the .csproj files from
> > archetype Or do you mean after running the JavaBinding, Pom Generator is
> > run again?
>
> Not sure about the implementation, just that I end up with two .csproj
> files after importing. It probably uses JavaBinding behind the
> scenes.
>
> > Do you mean the 2 csproj files ? Im not the author but my take on that is
> so
> > that VS can produce 2 separate binaries for main and test.
>
> Yes. I gather the 'build' in VS has no concept of a main artifact +
> associated tests.
>
> So when we talk about using a 'Test' directory within the main
> project, how is that going to work? As a nested VS project with a
> separate .csproj file? Or something that VS ignores and only NMaven
> knows how to build?
for VS it should be on a separate .csproj file to produce a separate binary
for it.
For NMaven it can be done 2 ways:
1. the test module can be define in testSourceDirectory,
2. have a pom.xml for the test module, declare the main module as a
dependency and then change the sourceDirectory to testSourceDirectory.
>
> > There's an Addin for Nunit , TestDriven.net (
http://www.testdriven.net)
> but
> > I'm not sure if this is commonly used in the dot net community.
>
> Interesting! I wonder does it handle compiling the tests or only running
> them?
>
> --
> Wendy
>
