On Fri, Aug 31, 2012 at 8:15 AM, Ruben Willems <[email protected]> wrote: > Hi > > Because that would require all the users of CCNet to update their > buildserver just to be able to run CCNet. > There are many companies where such an update is not that easily done, I > worked for one of them. > > It takes a lot of paperwork and time and effort to get this done, and since > CCNet will not use any of the new features, > why make an upgrade mandatory? > > > We still do not even use anything of .Net 4.0 specific :-) > an upgrade from .NEt 1.1 to 2.0 was neat : generics > from .Net 2.0 to 3.5 : Linq, anonymous types, lambda's, ... > > .Net 4 also has some neat features, but we do not require them for the > moment
Thank you for this. I can see how some people might want to force the latest version to try out all the "hot, new features" of the Framework, but if there isn't a compelling reason to actually *use* them, why force it? CCNet isn't a "fun project" to many of us regular users - it's a piece of business-critical operational software, and that means we can't just push a system update out into our environment on a whim. > On 31 August 2012 13:31, Katherine Moss <[email protected]> wrote: >> >> I don’t know specifics, I just see no reason not to require the highest >> .net framework version. What’s wrong with requiring .NET framework 4.5 >> because it’s the most current? >> >> >> >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Ruben Willems >> Sent: Friday, August 31, 2012 3:17 AM >> >> >> To: [email protected] >> Subject: Re: [ccnet-user] Support .NET framework >> >> >> >> Hi >> >> What things in 4.5 would be great for CCNet (buildserver / dashboard / >> cctray) ? >> I've got no clue for the moment >> >> >> with kind regards >> Ruben Willems >> >> On 31 August 2012 01:34, Katherine Moss <[email protected]> wrote: >> >> I think it a discussion that should be had then. >> >> >> >> From: [email protected] [mailto:[email protected]] On >> Behalf Of Steve Celius >> Sent: Thursday, August 30, 2012 3:53 PM >> >> >> To: [email protected] >> Subject: Re: [ccnet-user] Support .NET framework >> >> >> >> For CCNet, it is not about supporting the latest technology, you can >> configure your builds to make 4.5 stuff if you'd like to. >> >> It is about keeping the requirements for running the thing down, which is >> a good thing. Of course, there might be stuff in 4.0 and later that would >> ease development for the brave core-team, but that is another discussion I >> think. >> >> /Steve >> >> Katherine Moss >> >> 30. august 2012 21:48 >> >> Woe? No support for .net 4.0? You guys are missing out; think of version >> 4.5 as well. What are you thinking; why not always support the latest >> technology? >> >> >> >> From: [email protected] [mailto:[email protected]] On >> Behalf Of stevec >> Sent: Thursday, August 30, 2012 9:36 AM >> To: [email protected] >> Subject: Re: [ccnet-user] Support .NET framework >> >> >> >> Ok...good. That means I can continue to run XP on our CI box for a while. >> Thanks for the info, Ruben. >> >> Steve >> >> On Thursday, August 30, 2012 5:13:50 AM UTC-4, Ruben Willems wrote: >> >> Hi >> >> For the moment there are no plans for a move to .Net 4 if that is what you >> mean >> the current version 1.8 is at framework 3.5 >> >> with kind regards >> Ruben Willems >> >> On 29 August 2012 19:38, Stephan Clark <[email protected]> wrote: >> >> A quick question: I’ve got a CC-Net build server running on XP Pro. Will >> that OS continue to be able to run CC-Net for the foreseeable future (12-18 >> months)? >> >> >> >> Steve Clark >> >> >> >> >> >> Ruben Willems >> >> 30. august 2012 11:13 >> >> Hi >> >> For the moment there are no plans for a move to .Net 4 if that is what you >> mean >> the current version 1.8 is at framework 3.5 >> >> with kind regards >> Ruben Willems >> >> > >
