I've been bloging some about my experience using and playing with different parts of the Oslo stack on projects and articles. I've gotten a couple of reactions as to why it matters. I have covered some of it in my article series that focuses on DSLs and developers here:
Two weeks left before the Silverilght Tour hits Boston for Silverlight 2 and 3! If you want to be ready for the next version of Silverlight, this is the place to be. April 29st - May 1st in Boston, MA our three-day Silverlight workshop is going to teach the latest features of Silverlight as well as the complete Silverlight 2 stack.
When the Silverlight 3 "Out of the Browser" support (dubbed OOB by someone other than me) I was approached by more than a few attendees wondering whether I thought that OOB meant the death of WPF. While I still contend that this is not the case, I have been forced into thinking about the OOB support in a deeper way earlier.
I am running Win7 on my main box and I've been very troubled with the stability (if you've been to one of my classes recently, you know what I mean). The biggest trouble has been the startup time...sometimes Visual Studio will just timeout before IE launches. I couldn't figure out what was wrong and was hoping that moving to IE8 RTW would help.
|Using Visual Studio Code for ASP.NET Core Projects (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||126.96.36.199||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.25211.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|