Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


itsnotabug itsnotabug
  • xamarin 3

    @cbae: yikes, i can probably talk some higher ups into buying in, but those licensing terms would def be cost prohibitive if i were just starting out or wanting to play around with it as a hobbyist. i think they are squarely targeting enterprise with those terms. also, i'm not a fan of subscription based licensing.

    re: html/js... if someone came up with a ui abstraction that would mimic, pixel-by-pixel, the respective native controls' appearance and behavior, then i'd be all over it.

  • xamarin 3

    this looks like a huge update. xamarin.forms + the visual ui builder in VS is the holy grail for cross platform app development. can't wait to play around with it!



  • First Firefox OS phone finally for sale

    performance-wise, native will beat the pants off of anything interpreted, but FirefoxOS may be betting on the idea that it should be good enough for most basic apps. 'inferior' tech can succeed through ubiquity.

  • First Firefox OS phone finally for sale


    is that feasible?

  • js/dom templating from generics?

    i was just thinking how tedious it is to manually write out your templating js and dom for rich viewmodels. anyone know of t4 templates or other kind of scaffolding that you can use in the client after building up your complex viewmodel? i guess it'd be dependent on your templating library... my 1st thought was to extend object or List and use reflection/recursion to figure out which levels should be iterated over? just seems like someone may have already done this for the more popular templating libs / data-binding frameworks.

  • Microsoft open sources Roslyn compiler suite

    interesting... can anyone explain what they think the short term and long term practical outcomes of this move will be?

  • Understandi​ng the XBox One

    building apps for the living room against kinekt is definitely an exciting prospect. i bet there are entire classes of applications that haven't been thought of yet.

  • background thread in MVC

    hehe, not recommended... but i've even seen some projects get away with deploying the same solution twice, with a config bit that told the application start global handler whether or not this app would act as a 'service' node. isolate it into its own app pool and disable the web pipeline stuff and you have a poor man's node farm. makes development easier i'd imagine.

  • background thread in MVC

    it's generally considered bad practice to share your asp.net web request threads with 'worker' background threads. with that said, i've had success doing what you described for small apps that required flattening of complex viewmodels/expensive reporting stuff that i know won't ever get close to the max thread count (which is ridiculously low number by default... i think 50 or so?). i'd go with a dedicated windows service for anything big.

  • the expert :)

    yes, it's very well done. they hit upon so many subtle things...

    "what do i have to do with inflating red balloons?"

    "they're red"

    i about lost it at that line! :D