On Wed, Jun 25, 2008 at 10:51 PM, Wendy Smoak <
wsmoak@...> wrote:
> The Project Importer currently generates two .csproj files when run
> against the dotnet-simple archetype: one for the code and one for the
> tests.
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?
>
>
> From discussion on [1] and working with some simple projects, it seems
> to me that there should be a 1:1 relationship between pom.xml and
> .csproj files. (Slightly adjusted for the .sln file, which either
> gets a 'parent' pom of its own or else there is a pom.xml for a
> combined .sln and .csproj file.)
>
> However, I'm not familiar enough with the .sln and .csproj file
> formats to understand whether it is possible to tell Visual Studio not
> to package the tests along with the source code, if there is only one
> .csproj file. I assume there was some reason the author decided to
> create two different files?
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.
>
And how would you build the tests in
> Visual Studio (not using NMaven)?
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.
