Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
J

James McConville

@James McConville
About
Posts
3
Topics
0
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Newbie (but sort of advanced) Dependency Injection questions...
    J James McConville

    Yeah, I Agree, that example he uses is a bit dodgy but I can understand why he didn't want to write an entire DI engine for a beginners tutorial. Anyway, Like I say, I found it was an ok place to start before moving on to other stuff.

    WPF question visual-studio wpf game-dev regex

  • Newbie (but sort of advanced) Dependency Injection questions...
    J James McConville

    hey, I just started taking a look at this myself. Try the following - takes you through building your own (if very simple IOC).. http://weblogs.asp.net/sfeldman/archive/2008/02/14/understanding-ioc-container.aspx[^] Hope that helps.

    WPF question visual-studio wpf game-dev regex

  • Need help devising interview questions for a junior
    J James McConville

    You can work them out pretty quickly by not only asking the differences between interfaces and base classes but how and when it is best to apply each. I wouldn't bother asking silly questions like the number of piano tuners in london. Remeber, you're hiring a junior developer. They're likely to be a bit shy so don't terrify them within 2 minutes of the interview starting.

    The Lounge csharp json help question career
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups