Time to get serious about this ... how about an update from you Rocky ??
Anyone else have their toes in the water ??
/s
Perhaps there'll be more to say after this week's PDC conference.
But given the shift in focus of what was "Oslo" toward being a SQL Server focused tool, and away from being a general purpose DSL/model generation tool, it is arguably less valuable or relevant to CSLA .NET than it was before.
In the original vision it was potentially very compelling because it was about creating languages that compiled metadata into a repository so you could build a dynamic runtime to execute the repository metadata. See my blog for posts about MCsla and my research in that area.
That is all still possible with the latest CTP bits, and MCsla works with the latest stuff. It is a prototype or proof of concept, but it is interesting stuff.
However, if the SQL-focused direction means there's less focus on MGrammar and the concept of supporting dynamic runtimes (and that seems quite possible), then things like MCsla don't seem like such a nice fit any longer.
Seems like the "re positioning" has more to do with:
The following ... from the e-week story seems to indicate that there is MUCH more to come.
Moreover, Gall [the Gartner Analyst] said Microsoft has taken all of the Unified Modeling Language (UML) and written transformation rules in the "M" grammar. "So now they can map any UML document into a SQL Server database. And you can do all sorts of analytics on that," he said.
For his part, Gall said that in addition to Microsoft technologies such as SharePoint and others leveraging the Oslo, or SQL Server Modeling, technology, he sees opportunities for using the Oslo technology with the Microsoft ADO.NET Data Services technology, which was known by the code name "Astoria."
I ran into an application that uses the 12/05 version of the "DSL Toolkit" ..... is that worth looking into ??
I'm planning to take a deeper dive into OSLO and M to develop my DSL .... but am wondering if there is value in looking at "the toolkit"
Steve
Copyright (c) Marimer LLC