heh, I thought the peculiar thing was that it was just building the .NET
3.5 version randomly instead of being an actual deliberate change. I was
trying to think how that was possible. =)
On Sun, Jul 22, 2012 at 2:55 PM, Christopher Currens <
currens.ch...@gmail.com> wrote:
> It is, but I didn'
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
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...@wickedsoftwa
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
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 wrote:
>
>
>
>
> There was a commit for updating the build scripts - is there a command I
> can r
