Edward Moemeka

Back to Profile: Moemeka


  • Inside Windows Platform | Going from Windows Phone Silverlight to Windows RT XAML

    awesome video! Can you shed some light on when WinPRT will have ServiceModel and associated namespaces so we can *really* start porting.  All these samples are great from a UI perspective but don't include the tremendous amount of backend redesigning that needs to happen for a port to happen (becuase of lack of WCF stack). 

    Most of us built our WP Silverlight apps using WCF web services.  For some bizarre reason everyone keeps giving "LongListSelector" and "namespace change" examples; these are just about the least of anyone's concerns given the huge backend effort needed to commit to WinPRT

    For my part I spent a week converting one of my apps without even suspecting that such a thing would be ommitted and not clearly stated.  Then i right-clicked on my project searching for the "Add Service Reference" menu item and cried myself to sleep... 

    Please give us some good news, every release of your UI SDKs lately seem to be missing some obscure critical piece that just delays innovation and development. 

  • What's New In C# 6.0

    @MadsTorgersen:Thanks for you feedback, this request might be too late but please consider making anonymous types like new{Name="john",Age=5}; serializable by generating a public parameterless constructor for them and also marking the type with the appropriate DataMember/Contract attributes.  They are already public types and cannot be redefined at runtime so why not make them seriazable?  This reduces code bloat astronomically.

  • What's New In C# 6.0

    Um, what happened to the $ shortcut for dictionary initializers that have a string based key.  I get the squiggles when I try to use it.  This is a critical issue for data access types as you noted in a previous blog.  I am tired of creating one-off data classes that are just extensions of some back end projection.  The $ feature was a nice middle ground since anonymous types can still not be serialized properly.

  • Enterprise App Deployment for Windows and Windows Phone

    ...OR...you can just write your enterprise code in WPF (even web based) and not have to jump through 10000 hoops to get it installed.  Why would you make it so difficult to simply install an app, effectively making every other UI technology you have canibalize the use of WInRT and apps in the enterprise ?!?  What does one gain by using WinRT for LOB?  There is absolutely NO value proposition based on these deployment rules.  If you only use store compliant APIs then the store is best for deploying, if you dont then you are basically working three times as hard to make an application that will look (as of windows 10) and feel just like it's Native counterpart.

    You are shackling software development to IT guys who are: conservative, slow, and certainly dont have a passion for the technology.  Do you expect a VP on the Infrastructure team to approve such a process (maybe even have to train people!) just so I can build a cool reporting utility for my manager? 

    This type of approach is so strategic a choice, that it kills the ability for visionary technologists - who are *not* in senior leadership positions - to create enough of a ground-swell to make WInRT's merrits visible to people who *are* leadership positions.  But there is no simple way to explain to leaders what the actual value proposition of WinRT in this scenario is because its value is something only a visionary technologists could divine.  See the problem? 

    Please remove all these pointless restrictions because they really are idiotic. People can already install / run programs from anywhere and that is just not going to change. 

    I agree that there should be an API subset between store apps and normal apps, you can even put up a prompt or something every time a sideloaded app is run, but this madness has to stop. GET OUT OF YOUR OWN WAY!!!  And let us make this happen.

  • The New Windows Phone Application Model

    Hi Andrew,

     great presentation.  I definitely would love to migrate to 8.1 but it seems your team does not access web services or WCF.As you mentioned there are over 400,000 apps in the store, many of which use web services.  Is the expectation that we all go and rebuild our apps?  If so what is the rationale for such a drastic change and why not speak on it and provide examples as opposed to having us figure something like this out ourselves.

  • Anders Hejlsberg: Introducing TypeScript

    Thank you Mr. Hejlsberg, you and your team continue to build tools for those of us who don't believe in unnecessary complexity.  This language is the rational solution to the JavaScript problem.  It can be used in a web application interchangeably with javascript and offers all the important features of c# without creating some bizarre Frankenstein hybrid.

    This is common sense, and it only seems to come from your team these days.  Thank You!!

    PS - can you take over Windows Phone / Windows 8 development story please !!!!!

  • Visual Studio Toolbox: Visual Studio 11 Beta with Jason Zander


     thank you for the absolutely AMAZING tool!  Can you please do us some of us a favor and provide a setting page for the Artboard like expression blend has.  There does not seem to be anything like that.  Specifically, if would be nice to have a way to toggle the behavior of Mouse Scroll.  For me, see the default behavior as to scroll (like how it is everywhere else) and if I want zoom then I *modify* that behavior by explicitly holding down on the control, alt or whatever button.  In VS11 it defaults to Zoom which is essentially inconsistent with everything in Visual Studio and I dare say inconsistent with default Windows Behavior (vis-à-vis internet explorer, explorer, metro apps, New Start Screen).  This is the one place where it is reversed for what seems to be no reason.  Wouldnt anyone, designer or otherwise *use* scrolling around the screen more than zooming ?!?

    Please change this or at lease give us an option.  The new Artboard *is* awesome.  Windows 8 is awesomer-er

  • Future directions for C# and Visual Basic

    @bcooley: wow,  that is a really nasty post.  What you fail to realize is that Roslyn will make AOT very easy since c# code can be *dynamically converted into C++* and then *compiled as native*.  Try to use your imagination for positivity instead of being negative and rude!  This takes C# light years ahead.

    Furthermore c# 4.0 was just recently released, even though they call this c# 5 (marketing) I think this is more of like the 2.0/3.0/3.5 pattern we saw in the past (hence no *actually* new runtime version). 

  • Windows 8 Running on ARM

    @electrookosh: that's because the alleged "ARM version" seems to be a remote desktop into the x86 version.  That's the reason why the camera zooms in when they interact with it and when the camera zooms out, the x86 version is magically on the same screen as the ARM version.  Tune in next week to see Microsoft make the Statue of Liberty disappear Wink.

    Regardless of all that, MS simply GETS IT.  No one else seems to understand that a tablet *should* also be a PC.  (well I guess Motorola Atrix did but rather than execute they simply gave a dumb terminal into the phone).  I am writing this post on a windows 8 PC and I have no reason to look back.  Well done Microsoft!

  • Allen Wirfs-Brock and Chris Wilson: EcmaScript, JavaScript and the Web

    I know javascript rules, but I just always feel like i'm stitching things together with it.

  • Allen Wirfs-Brock and Chris Wilson: EcmaScript, JavaScript and the Web

    will there ever be a new compiled language for the web?  One that all the browsers will understand?  I really wish that something else existed beyond javascript.

  • Where the Multitouch Devices Are pt. 2

    My touch smart tx2 from HP went from a buggy 4 touch points a month or so back to only 2 touch points after installing the latest N-Trig driver.  How many touch points is this device supposed to have?  Should I be calling someone at HP? 


    I think that MS should back us consumers and force these companies to include information about how many touch points the devices have on the packaging and or technical documentation.  As it stands you have no clue until you actually fire up your laptop or PC how many fingers it will work with.  Help me out.