nashvillebas.blogg.se - Rad studio 2009 stack overflow

RAD STUDIO 2009 STACK OVERFLOW MANUAL
RAD STUDIO 2009 STACK OVERFLOW CODE

RAD STUDIO 2009 STACK OVERFLOW CODE

The aim was simple: everyone has about 2 and a quarter hours (including a break for food) to write the code to implement their player. Write some code to implement your player!.Create a class that implements IGamePlayer (make sure to include necessary export attributes).Add reference to IConnect4Player (project).Add reference to ComponentModel (project).What each person had to do to implement their 'player': An identical sample player written in VB.NET.A copy of MEF Beta 2 Preview 8 (which was used to load players from the individual DLLs).A library containing the interface that each player was required to implement.A set of tests to verify the logic in detecting wins, etc.A WPF user control to represent the game board.

RAD STUDIO 2009 STACK OVERFLOW MANUAL

(This host also allowed manual playing of each player.)

A WinForms 'host' application which displayed the board, managed 'players', etc.

What I provided for those who came along to use: This was deliberately not made known before the event so no-one could get a headstart on working out any game logic or tactics. If you've scanned down to the image below you'll see that the game used was Connect 4. If you want to make it possible for people with varying skill and experience to be able to achieve something in the time limits things further. Writing something productive and fun in about 2 hours is actually quite hard. My initial expectation was that this may not be a popular event - after all I'm not aware of any other user groups having done an event like this before. In addition to having each persons 'player' compete against each other we'll also look at the way each person approached the problem and how successful that was. It will be practical to achieve something good in the time frame available and plenty of examples will be provided to get you started.

The logic therein can be as simple or complicated as you want to make it. Don't worry if this sounds complicated, it will only involve implementing an interface containing 4 methods (and one of them just returns your name!). The plan is for everyone to write automated players for a simple game. That's what we hope to do at the CodeFest. While it can be good to learn by hearing people present and demonstrate new techniques, it can also be good to learn by seeing how different people solve the same problem. (Yes, the name wasn't very good but the event was.) One of the things I've been keen to do at DevEvening is to see what would happen if we did a session where everyone came and wrote code.įor this reason we had an event and called it the 'Christmas CodeFest'.