It is, but I didn't want to deal with changing our CI server configuration to get what is a little bit of benefit (at the moment) for the amount of time it would have taken me to figure it all out. At the moment, the kind of packaging we need for a release would be both frameworks, so as of now, I have it outputting both. I am not oblivious to the awkwardness of the build scripts how they are now, as the most glaringly obvious flaw with outputting both, is that nunit runs the tests for .NET35 and .NET4 at the same time. There are several things wrong with the way that works.
It's not a hefty change, though, that needs to be done if you wanted to change it to a build parameter, I have a mostly finished patch for that since that was original first goal. There's an extra build step that can be removed and a variable added to each project page. The larger(?) change would the actual packaging for NUnit. Even though it's already it's own separate target, I'm sure we want to validate that both .NET35 and .NET4 builds have been run before packaging the output. Thanks, Christopher On Sun, Jul 22, 2012 at 11:27 AM, Michael Herndon < mhern...@wickedsoftware.net> wrote: > that is a peculiar behavior. > > On Sun, Jul 22, 2012 at 4:41 AM, Christopher Currens < > currens.ch...@gmail.com> wrote: > > > Right now, it outputs both automatically. I didn't put in a switch, it > > just does it be default. > > > > > > On Sat, Jul 21, 2012 at 2:38 PM, Michael Herndon < > > mhern...@wickedsoftware.net> wrote: > > > > > you would need create a build variable for the .net framework version > > > parameter for msbuild and have it run a second build and switch out the > > > version. > > > > > > On Sat, Jul 21, 2012 at 3:08 PM, Prescott Nasser < > geobmx...@hotmail.com > > > >wrote: > > > > > > > > > > > > > > > > > > > > > > > There was a commit for updating the build scripts - is there a > command > > I > > > > can run to output both 4.0 and 3.5 binaries of everything? > > > > > > > > > >
