Comments on: OSS and the .NET Framework upgrade http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/ Strong opinions, weakly held Wed, 22 May 2013 13:39:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Jon http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2540 Jon Mon, 09 Aug 2010 10:37:27 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2540 Yep, go with the branch/bugfix only option for VS2008/.NET3.5 and move onto VS2010/.NET4.0 asap. Yep, go with the branch/bugfix only option for VS2008/.NET3.5 and move onto VS2010/.NET4.0 asap.

]]> By: tracker1 http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2539 tracker1 Fri, 06 Aug 2010 18:29:35 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2539 I'd go for the branch myself. I think the uptake on 4.0 is much smoother than say 1.1 to 2.0-3.5 for the most part everyone I know is at least researching the move at this point and plans to do so by end of year... as long as going from the 3.x version to the 4.x version is relatively smooth it should be fine... just try not to break anything (change too much) for the next year or so... adding stuff is fine though. I’d go for the branch myself. I think the uptake on 4.0 is much smoother than say 1.1 to 2.0-3.5 for the most part everyone I know is at least researching the move at this point and plans to do so by end of year… as long as going from the 3.x version to the 4.x version is relatively smooth it should be fine… just try not to break anything (change too much) for the next year or so… adding stuff is fine though.

]]> By: Chris Sutton http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2538 Chris Sutton Fri, 06 Aug 2010 02:20:20 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2538 Take full advantage of .NET 4 on the main branch and just provide fixes for the VS 2008 version. Take full advantage of .NET 4 on the main branch and just provide fixes for the VS 2008 version.

]]> By: bogardj http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2537 bogardj Thu, 05 Aug 2010 21:56:33 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2537 @Jeremy Branching it :) @Paul I'm not sure that fixes the .NET 4.0 vs .NET 3.5 issue, does it? @Jeremy

Branching it :)

@Paul

I’m not sure that fixes the .NET 4.0 vs .NET 3.5 issue, does it?

]]> By: Paul Cowan http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2536 Paul Cowan Thu, 05 Aug 2010 16:05:01 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2536 Do what castle do and have a VS2008 solution and a VS2010 solution. Use the framework version as a switch to what is getting built. Do what castle do and have a VS2008 solution and a VS2010 solution.

Use the framework version as a switch to what is getting built.

]]> By: Jeremy http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2535 Jeremy Thu, 05 Aug 2010 15:34:27 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2535 Branch it, so at least it will use the right terminology. :) In all seriousness, I truly doubt that forking it, whether in the Git interpretation of the word or not, is what you or any of the other commenters intend. Do you really want to maintain it as two separate repos? Or, more likely, as two branches in one repo. Branch it, so at least it will use the right terminology. :)

In all seriousness, I truly doubt that forking it, whether in the Git interpretation of the word or not, is what you or any of the other commenters intend. Do you really want to maintain it as two separate repos? Or, more likely, as two branches in one repo.

]]> By: phil http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2534 phil Thu, 05 Aug 2010 14:48:17 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2534 get a fork'n move on. get a fork’n move on.

]]> By: Jeff Doolittle http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2533 Jeff Doolittle Thu, 05 Aug 2010 14:47:52 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2533 I seems that Moq handled this with multiple versions: http://code.google.com/p/moq/ I seems that Moq handled this with multiple versions:

http://code.google.com/p/moq/

]]> By: Jason Meckley http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2532 Jason Meckley Thu, 05 Aug 2010 14:39:45 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2532 I'm one of the VS 2008 .Net 3.5 devs. The same conversation just arose regarding the Rhino stack. A Fork for 3.x seems to be the common solution. I’m one of the VS 2008 .Net 3.5 devs. The same conversation just arose regarding the Rhino stack. A Fork for 3.x seems to be the common solution.

]]> By: Henning Anderssen http://lostechies.com/jimmybogard/2010/08/05/oss-and-the-net-framework-upgrade/#comment-2531 Henning Anderssen Thu, 05 Aug 2010 14:36:36 +0000 /blogs/jimmy_bogard/archive/2010/08/05/oss-and-the-net-framework-upgrade.aspx#comment-2531 Fork and bugfix existing version and all new development should be on .net 4.0 Fork and bugfix existing version and all new development should be on .net 4.0

]]>