My MSBuild.NUnit project, can be of help (See https://github.com/monoman/MSBuild.NUnit ). The main assumption is that you can add the reference to the task assembly in msbuild proj file as an "implicit" reference to the matching framework/runner assemblies (a parallel non-GAC installation), so avoiding versions mismatches. The Nuget that the project generates uses that assumption and shares a NUnit installation for the many projects in a solution, but the one-project-per-solution approach make this less efficient (although workable).
Just my contribution to the discussion, Rafael "Monoman" Teixeira --------------------------------------- "We live in a world operated by science and technology. We have also arranged things so that almost no one understands science and technology. This is a prescription for disaster. We might get away with it for a while, but sooner or later this combustible mixture of ignorance and power is going to blow up in our faces." -Carl Sagan On Mon, Feb 14, 2011 at 9:29 AM, Marek Safar <marek.sa...@gmail.com> wrote: > Hello, >> project will require NUnit addin (am not sure if it exists for 2010) and >> thus excludes Express users. > You don't need nunit addin, you can use any internal or external tool > which can run nunit including nunit-console. The trouble is to build > with correct nunit framework version to be able to use the tool. > > Marek > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
