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


William Kempf wkempf
  • Getting a property name as a string.

    In your case, "static reflection" may be better. http://www.digitaltapestry.net/blog/reflecting-on-code

    Keep in mind that reflection is slow, whether it's runtime reflection or static reflection. It's best to find ways to cache the results and not use reflection every time.

  • Win Phone 8.1 beef.

    @cbae: I made a suggestion on User Voice some time ago related to this, and I really wish they'd implement it. http://windowsphone.uservoice.com/forums/101801-feature-suggestions/suggestions/2285775-driving-car-mode

    We have driving mode. Apps should be able to detect when the phone is in driving mode so that they can provide simpler, safer, interfaces. (Yes, you're correct, an appropriate interface is no less distracting or dangerous than turning on your radio, adjusting the temperature, turning on your wipers, etc. So @spivonious is off base here.) Even the start screen should be customizable when in driving mode. For Xbox music all of the interface for selecting songs could be removed, forcing you to use voice control, which is safer. The display would just be the cover art with swipe gestures for pause/play and next/previous tracks. Audible has a nice "button free" interface (well, nice other than it's ugly) that would work great for its Driving Mode Display.

    Like I said in my User Voice response, we shouldn't be limited to just Driving Mode either. Allow other modes to be defined as well, so we can limit the apps available, change the volume settings, turn on auto replies, etc. for each mode. Then we could have a Work mode, a Church mode, a Movie mode, etc. You should be able to manually switch to any mode via the new Action Center, and you should be able to define events (time of day, logging on to specific WiFi or Bluetooth devices, tapping certain NFC tags, etc.) that will automatically switch you to a specified mode. This sort of personalization would put WP ahead of other platforms (which are currently ahead because they can already do a good portion of this).

  • Xamarin and MSDN

    , RealBboy360 wrote


    Well yes, if you have to scan, print, use video cam,  or other stuff like that you might have to wait until the javascript plugins or cordova... catches up.  I probably wouldn't use Xamarin for that either.  But if I were to bet on which one will be there first, I'm going with javascript.  Why not be able to re-use the code for your website?


    That's funny, because Xamarin can already do all of that. As for the web site... first, not all mobile applications have (or even could have) an equivalent web site. Second, if you have a web app, why would you or your users want it repackaged as the exact same application just running out of the browser (sort of). Third, if you follow proper architectural design it's possible to reuse a good portion of your code even on your website. Yeah, you'll reuse more if you go full HTML/JavaScript, but your mobile apps will suffer for that decision since your UI will not be "native" and follow the design aesthetics of the platform.

    Again, I doubt HTML/JavaScript will ever even be the dominant choice here. I've written complicated applications using that tech in the past. I don't care to do so again. Certainly not for "native" apps. Your welcome to hold a different opinion, but there's NO evidence that your opinion is shared by the majority. Currently the majority opinion seems to be to create non-portable native apps for each platform, actually.

  • Xamarin and MSDN

    @figuerres: I'll say never. I find it unlikely that it would become the predominant set of tools for creating apps, but I guarantee it will never "kill of all other app development".

    Heck, even within the world that it shines people are working hard to "replace" it. TypeScript, CoffeeScript, Dart, etc. are all attempts to replace JavaScript, and then there are the crazier stacks that try to replace HTML with WebGL or some other tech.

  • How would you define "Modern C++ and Modern C++ practices"?

    Don't like Boost? Most of what's in modern C++ came from Boost. Don't quite get that. I can fully understand saying you don't want to use Boost, but not liking Boost but liking modern C++ makes little sense to me.

  • Office for iPad

    To be fair, everything your giving kudos to Nadella for was actually already in the works under that evil "Ballmer" that made all of the past decisions you've been critical of. We've yet to really see what Microsoft under Nadella will be like. :)

  • Definition of a lower-class developer:

    Who's cheering this on? I've not seen a single person, developer or otherwise, cheer about this.

    Like others have said, the patent system is a disgrace. However, it exists, and anyone not playing by its rules is being foolish and is sure to pay for that decision. I won't cheer anyone on for doing this, but I will chuckle at the people who get indignant about someone doing it.

  • Are emoticons racist?

    Seeking greater racial diversity != Apple thinks emoticons are racist.

  • Official ​Announcemen​ts for Killings?

    @Jim Young: The plug-in is as good as dead. No support for it in IE in Metro, for instance. Have one of the major browsers change their plug-in model enough to break the existing plug-in and I guarantee you MS won't update it to work. Sorry, I can't consider Silverlight to be anything other than dead.

  • Official ​Announcemen​ts for Killings?

    , Vaccano wrote

    Does Microsoft ever do official announcements when it kills off a development tech?

    The ones that have affected me did not have announcements that I know of.  (Those are Linq To SQL, Silverlight, Smart Device Projects and general focusing away from Enterprise and to Consumer development.) 

    I have usually found out via a comment on a Microsoft blog or an MSDN Documentation page.  (I mention this because it seems WCF Data Services has been killed off that way too.)

    This seems like a very frustrating way to communicate such disappointing news.  Is there a reason that they do it this way?  (Rather than an official channel where at least a few reasons can be given.)

    I know Microsoft has a bad reputation here, but really, it's only recently that Microsoft is truly guilty of "killing off" API stacks. LINQ to SQL? You still can use it, and from day one Microsoft told you that would be shortly replaced by EF. Silverlight I give you. Yeah, they really and truly killed that one off, and it was stupid. I know very little about Smart Device Projects, but I still find documentation for it and assume it's still supported... of course CE is basically dead, but it died naturally. WCF data services isn't dead, it's just not the preferred way to skin that cat now. Web API has proven so much easier to work with that people are just naturally choosing it over WCF rather frequently, and Microsoft is going where their customers are. WCF isn't dead, it's supported and in use and will likely even get updates, but the direction has changed and not necessarily through Microsoft's actions.

    If Microsoft dropped support, I'd say an official announcement is warranted. That's why they've got a bad rep here... they really messed up with Silverlight. But, mostly, devs seem to want to make a mountain out of a molehill. Technology changes at a break neck speed... if you're not ready, willing and anxious to keep up, maybe you've chosen the wrong profession. The other side of that coin, just because things have moved on doesn't mean you should drop or rewrite that application that's fulfilling a need using the older (still supported) tech.