All Visual Studio blogs in one place

AddThis Social Bookmark Button
I’m just coming back from Build 2014 and it was a great pleasure to talk to customers/developers.  It is one of the best parts of my job right now in seeing how customers use the technology our team represents.  If you are a XAML developer and didn’t have a chance to go to Build or haven’t watched all the sessions, here’s a quick short list of recommendations I’d have: Common XAML UI Platform overview (Tim Heuer) XAML UI Controls (Shawn Oster) Developing across multiple
form factors (Peter Torr) What’s new with Windows Phone Silverlight apps (Sam Jarawan and Harini Kannan) Using VS to build universal Windows apps (Navit Saxena) There are many more (app model, localization, accessibility, tiles, notifications, etc.) so please do look at the event site and download/watch your favorites.  I think the list above gives you a good intro to the UI area changes and introduction to the concepts of Universal Windows apps.  If you haven’t heard of that concept yet, you can jump to the Keynote from...(Read whole news on source site)

AddThis Social Bookmark Button
I had the enormous thrill to talk with Scott Meyers (of Effective C++ fame) on my Podcast this week. If you write C++ or even used to write C++, then Scott is likely as important to your career as he has been to mine. Talking to him this week included how he got started, how the C++ spec has evolved and how much better Oregon is as related to California. The Hello World Podcast is where I get to talk with some of your favorite authors, developers and speakers about how they got started in software development. You
can listen to episode 20 here:  You can subscribe to the podcast here:
AddThis Social Bookmark Button
AutoMapper is one of the essential tools in my ASP.NET MVC toolbelt.  I use it on every MVC project I do.  It's saved me countless lines of code over the years.  And yet, there's always been one thing that bugged me about it: it violates the idea of "common closure."  I've built a better way to handle this, but as my friends have accused reminded me, I might have forgotten to share this approach publicly.  Until now. With AutoMapper, you typically place your mapping configuration in a completely separate profile class, which creates an artificial barrier between
two things that are likely to change together: your view model and its mapping definition.  I came up with an alternative many years ago, but as my "friends" have pointed out, I apparently haven't blogged it or talked about it openly before my Pluralsight course.  To try and make up for that serious misstep on my part, I've extracted the relevant part of my Pluralsight course and made it available for free on YouTube.  You can check it out here: ASP.NET MVC - Better Conventions for AutoMapper. Full disclosure: this is a small piece...(Read whole news on source site)



Enter your email address:

Delivered by FeedBurner

Increase your website traffic with


Anti-spam: How many eyes has a typical person?

Follow us on FB