Jibble

Author Topic: Transition to .net 4 - request for AGS 3.4.0  (Read 5526 times)

tzachs

  • Mittens Vassal
  • AGS Baker
  • Parking Goat- games that goats like!
    • I can help with translating
    • tzachs worked on one or more games that won an AGS Award!
    •  
    • tzachs worked on one or more games that was nominated for an AGS Award!
Re: Transition to .net 4 - request for AGS 3.4.0
« Reply #20 on: 02 Jan 2014, 14:33 »
I support this, especially if it's compatible with XP.

@Radiant, I don't think there's anything specifically needed by AGS, but it will make life a lot easier for developers, thus you'll get more productivity. Linq alone could probably have been used to reduce the amount of code by one fifth (wild and unsupported claim).

Re: Transition to .net 4 - request for AGS 3.4.0
« Reply #21 on: 02 Jan 2014, 14:42 »
Linq alone could probably have been used to reduce the amount of code by one fifth (wild and unsupported claim).
And reduce readability by half (wild and unsupported claim)(laugh):tongue:.

Radiant

  • Mittens Knight
  • AGS Baker
  • Return once more to the Two Kingdoms!
    • I can help with publishing
    • I can help with story design
    • Radiant worked on one or more games that won an AGS Award!
    •  
    • Radiant worked on one or more games that was nominated for an AGS Award!
Re: Transition to .net 4 - request for AGS 3.4.0
« Reply #22 on: 02 Jan 2014, 17:40 »
@Radiant, I don't think there's anything specifically needed by AGS, but it will make life a lot easier for developers, thus you'll get more productivity. Linq alone could probably have been used to reduce the amount of code by one fifth (wild and unsupported claim).
I'm sorry, but with a large change as this, I would really want to hear more concrete examples of what and how it makes easier for developers. For multi-person projects, I'm not a fan in general of migrating to a newer version of anything without a solid concrete reason. $.02