maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Moved: (MSANDBOX-16) VStudio Project generated by CSharp VStudio Plugin doesn't support NUnit appropriately
Date Mon, 18 Jun 2007 00:41:57 GMT


Brett Porter moved MNG-2372 to MSANDBOX-16:

    Component/s:     (was: Sandbox)
            Key: MSANDBOX-16  (was: MNG-2372)
        Project: Maven 2.x Sandbox  (was: Maven 2)

> VStudio Project generated by CSharp VStudio Plugin doesn't support NUnit appropriately
> --------------------------------------------------------------------------------------
>                 Key: MSANDBOX-16
>                 URL:
>             Project: Maven 2.x Sandbox
>          Issue Type: Bug
>         Environment: Windows XP
>            Reporter: James Carpenter
>            Assignee: Brett Porter
>         Attachments:
> The csharp vstudio plugin spins up a csproj file for an individual csharp maven module.
 (No multi-module support currently exists.)  For some strange reason the nunit dependencies
provided as resources to the VS project, don't work correctly with the TestDriven VS plugin.
> To work around this issue, I extended the vstudio plugin to support the inclusion of
resources specified with an absolute path as well as the ability to exclude dependencies from
the resources included in the generated csproj file.
> The excludedDependencies functionality is more or less what it should be, but the references
tweak is a bit hackish.  The reference support should actually be changed to support subsections
for each directory references are coming from.
> ==========================
> Example References Suggestion
> ---------------------------------------------
> I now have:
>                <references>
>                         <reference>
>                             <path>System.dll</path>
>                             <gac>true</gac>
>                         </reference>
>                         <reference>
>                             <path>C:/Program Files/NUnit 2.2/bin/nunit.core.dll</path>
>                             <gac>false</gac>
>                             <absolute>true</absolute>
>                         </reference>
>                 </references>
> A better solution would be something like the following:
> <references>
>                         <reference>
>                             <path>System.dll</path>
>                             <gac>true</gac>
>                         </reference>
>                         <referenceGroup dir="C:/Program Files/NUnit 2.2/bin/">
>                             <reference>
>                                 <path>C:/Program Files/NUnit 2.2/bin/nunit.core.dll</path>
>                                 <gac>false</gac>
>                             </reference>
>                         </referenceGroup>
> </references>
> This may not be quite right, but I suspect you get the idea.
> ===========================================
> Background on the Importance of the TestDriven Plugin
> ----------------------------------------------------------------------------
> Being the !@*% IDE that it is, MS Visual Studio .NET 2003 doesn't have built in support
for NUnit (in the xUnit family).  The TestDriven VS plugin ( provides
the ability to right click on an nunit test and run it.  One can thereby obtain functionality
similar to the junit support built into IDEA,  Eclipse, etc.
> =========================================================
> Differences between my Plugin's POM and the one in the Maven Sandbox
> ----------------------------------------------------------------------------------------------------
> The attachment below contains my changes.   As there is no release version for the csharp
plugins, I have created my own in-house versions simply to keep them from unknowingly moving
under my feet. I strongly suspect the in-house csharp plugin versions are still identical
to that in the maven plugin sandbox, but I havn't actually checked. My in-house copies were
built from maven SVN copies only a few weeks ago. You will need to change the version numbers
of the plugins in the attached example project.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message