Do you do cross-platform development on .NET? Are you sick of #ifdef hell or maintaining duplicate codebases which do essentially the same thing? Let me show you Portable Class Libraries. They're neat.
Things to cover:
- why on earth should i care?
- how do you even make a portable library? and what is this magic?
- dude where's my XYZ API?
- how can you mash platform-specific APIs together with portable APIs?
- the piece de resistance - what a real-life PCL app looks like
- this shit works with NuGet are you not entertained!
- oh and the Mono guys are kinda sorta supporting it too
You've probably heard about this 'git' thing. You've probably heard from people who love it and people who hate it. You might have even tried it out.
But what happens when more than one developer starts working in the same git repository? What about fifty developers? What about more? How do you manage that "D" in DVCS anyway?
So gather round and I'll share some anecdotes from the git trenches (doing open source work on GitHub and working for a year in a large team which uses git internally). This won't just be a group therapy session, as I'll mix it up with some tricks I've found to help ease the learning curve.
Things to cover:
- where's my GUI? [ oh no not the old tooling discussion again ]
- this is too hard i'm going back to svn [ having a git flow that doesn't suck ]
- oh shit i just messed up my repo [ how to get back to a happy place ]
- merge push reject merge push reject merge push reject curse curse curse [ how to keep your sanity in a large team ]
- i'm just working in master why is that bad [ branches are free. you should abuse them. ]
- great now i'm stuck under all these branches [ strategies for release branches and managing bugfixes ]