YA.NB - Yet Another .Net Blog

As you install .Net 4.5, some of your applications may seem broken and not working anymore. This goes back to the fact that the .Net 4.5 installer removes the Client Profile Versions of the framework. Now, I think about the Client Profile what I might,but it would have been great to get a small note about this important change during the installation of VS 2012... Further info can be found here .

Any Developer working in the XAML Environment must have stumbled across Microsoft Blend, a.k.a. Expression Blend at some time. Blend is a Software aimed to support developers and designers of XAML based UIs create designs and animations, apply behaviors and so forth. As of 2010 (talking VS Versions), Microsoft has made the licensing of Blend a real mess, if you're a WPF Developer: The only way to purchase Blend is buying the entire Expression Studio Ultimate for somewhere around 500 Euros. Smaller development teams are made to bleed unnecessarily, since the VS 2010 XAML editor had serious issues before SP1. We're talking 2012 now - seems MS have learned their lesson: Blend is free for Windows 8 Store Apps and comes along with the correlating Visual Studio Express Edition. But what about WPF or the already zombified Silverlight? Good news first: Blend will continue to support WPF. But what are the licensing terms? Looking things up on the Blend Insider Blog , I fo...

Earlier today, Microsoft have officially release their  TEAM FOUNDATION SERVICE . It's absolutely justified to capitalize this, because what we get here is a freebie that's catering for all the needs of a small developer team (up to 5 nerds can ride for free). Thanks a lot, Microsoft, for this great christmas present.

I am absolute and unrestricted proponent of the Windows Presentation Foundation , and I think I cannot say this often enough : It makes things easier and more structured. And I love it, somewhere close to every day. Now, as three quarters of this year have passed by without any significant smoke rising, I have also had the chance to get to grips with Workflow Foundation , and was literally astounded to see how far Microsoft has taken the idea of XAML (Yes, I'm a bit late to that party).  Combining the two technologies was the next obvious step, which worked fine until yesterday.  Here's the story:  In my somewhat completed WPF UI, I added a WF Activity. An instance of that Activity could not be created, Visual Studio kept throwing "Namespace or Type not found" like it was candy. Funny, though, that intellisense proposed both the class and the containing namespace of the Activity. A more complete description of the issue can be found in my StackOver...

Anyone interested in giving Visual Studio 11 a temptative go, head over here and get it:  http://www.microsoft.com/visualstudio/11/en-us/downloads Happy Debugging!

Whoever was happy enough to get the chance to implement a WorkflowFoundation-based solution knows the ultimate power that comes with the Framework. If you haven't tried WF yet and are curious to try, you should do yourself the favour to watch the MSDN screencast series by Maurice de Beijer, located here . This is as good a round-up of the technology as I can imagine and deserves a great deal of attention. I really can't imagine why those videos have so little views...

After mobile Flash has been jilted, there's (more or less official) word out on the street that Silverlight 5 will be the last iteration of Microsoft's web interaction platform. Eventually, HTML5 seems to be the next big thing, and among many other reasons for the first major release of the web standard in ages, the following make most sense for me: No Framework or runtime required  open specification in future, every browser will implement it without a plugin (bringing an end to license hell) Microsoft sure knows how to amaze developers, and with the incarnation of XAML, have given us a toolset that enables us to develop for the web, the mobile and the windows platform in the same comprehensible way. HTML5 is supposed to do the very same thing, and in addition enable us to develop for iOS and other non-.Net-aware platforms as well, all with the help of JavaScript (yuck!). That's what I call zombie technology : I thought JS was dead, but here it comes, stabbing us ...