This last week or two has seen a number of interesting stories come out of Microsoft (some official, some not official), especially as it relates to developers and writing code. While I am sure that the announcements are not meant to indicate a trend, taken in conjuction they are confusing or disheartening to developers.
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:
I had a great time at the SQL Saturday in Atlanta today. I did two talks: Using MSchema and ADO.NET Data Services for DBAs. If you were there, thanks for attending. If you wanted to grab the code and slides, follow the link above!
If you haven't been following the new Specification for the M Language that the Oslo team has been cooking up, they have been making changes in response to feedback about the language. These changes will come to light in the next CTP. These changes are;
If you're in Atlanta tomorrow (October 27th, 2008), stop by the Atlanta .NET User Group to see me talk about Domain Specific Languages. I am doing the short session to get you ready for Oslo. Its going to be too soon after Oslo's unveiling to show you anything about Oslo, but I think the important point here is that DSL's are an important part of development whether you know it or not.
Head over to the Chris Sells' blog to get all the details on the new public CTP of Oslo. This toolset has the possibility to change the nature of development in a major way. If you are interested in the modeling or DSL space, its definitely worth your time to dig into the tools.
When I first grabbed the Oslo SDK, I wanted to first dive into MSchema. MSchema is a language for defining your data store and relationships between data that Oslo uses to define how to handle storage. My first attempt was to try and replicate the store model of my VideoGameStore data that i've been using to show off Silverlight and ADO.NET Data Services. My original attempt was:
Now that Oslo is in a public form, I've taken time (as you probably noticed in earlier blog posts) to look at Oslo. While the Model Driven Development part of the stack is important and potentially game changing, I wanted to stop and look at the Domain Specific Language part of the Oslo stack.
I am not the only one though. The potential for building Domain Specific Languages has caused jeers and leers from different parts of the web including Martin Fowler, Frans Bouma, and Roger Asling. Aside from the whether "M" becomes a valid way to build Domain Specific Language, I am more interested in the idea behind Domain Specific Languages themselves.
Coming December 16, 2008, i'll be at the Atlanta stop of the MSDN Developer Conference to see the PDC content. These events will give you an opportunity to see the Azure platform, Windows 7, Silverlight, F# and even Oslo.
I've spent the better part of six weeks building the new AgiliTrain website and its been quite a lot of fun. Of course if you have been reading this blog for long you know that I usually take a personal project like this as an opportunity to learning something new. In this case I did three things I haven't done on a personal project before:
The CSD folks have released a new CTP of the Oslo toolset. This release contains the same set of tools as the October 2008 CTP (nope, no Quadrant yet) but hopefully some of those pesky MSchema and Intellipad bugs will be gone. I'll let you know when I get deeper into the bits. Go grab it here:
In Part 1 of this series, I talked about why I used MVC to create my new venture. In this second part, I will talk about how I implemented MVC.
When I decided to implement MVC, I was very new to it so there is some code in the site that reflects that. The later code and the code I've gotten around to refactoring is much cleaner, but working code is working code.
|Implementing and Securing an API with ASP.NET Core (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||220.127.116.11||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|