Search results matching tag 'PDC08'

Cloud service in Azure : Speedtraps

Dennis van der Stelt — Mon, 23 Feb 2009 12:52:51 GMT

For the 828 event next Thursday I’m developing some examples. One of them is where I get all speed traps (Flitsers in Dutch) from http://www… a source that I won’t mention here. I then want to expose these via WCF via SOAP and REST. Of course this will be so extremely popular, that I have to use Windows Azure and be able to scale immensely so you folks won’t miss out on the latest speed traps.

Anyway, after first writing “w00t” in the cloud, I now got my first WCF service in the cloud which actually does something.

You can find the REST version here:

http://flitsservice.cloudapp.net/speedtraps.svc/Flitsers
http://flitsservice.cloudapp.net/speedtraps.svc/Status

And the root location, including MEX and WSDL stuff right here:
http://flitsservice.cloudapp.net/speedtraps.svc

Unfortunately you won’t be able to add a reference (proxy class) because of some internal stuff going wrong inside Azure. But maybe I’ll supply you in the future with that as well, and even a client application. Maybe I’ll create an syndicated version of it, but for now you can read the REST version and use it in your own apps. I have no idea how long this will run though.

PDC 2009

Dennis van der Stelt — Tue, 04 Nov 2008 08:51:24 GMT

We’ve already heard it mentioned last week in Los Angeles, but here’s the date already…

Entity Framework Futures

Dennis van der Stelt — Tue, 04 Nov 2008 08:46:24 GMT

A bit late, but it was still in my drafts folder, I just had to finish it. Timothy Mallalieu presented the session on the future of Entity Framework.

The Data Platform
We have so many data storage options and so many needs for data.

Normal data access
Users and applications get data from the database via frameworks or libraries
Integration/aggregation sync
We get data from the cloud, services, databases, etc.
Reporting
Reports get data from a data warehouse
Management, deployment, policy & security
We have metadata stored in XML, databases, etc.
Models and workflow
We have all kinds of models and workflows needing data.

The question is, how do I get the data I need? There are a lot of options currently.

Core Storage
Data access API’s and frameworks (like ADO.NET)
Mid-tier frameworks and technologies (like Astoria)
Client technologies (custom build, with as example dynamic data)

Entity Framework and EDM are the start for creating data-models and retrieving data. Those were released with .NET Framework 3.5 SP1, but there’s much more to come, starting with SSRS (SQL Server Reporting Services) and synching data for offline usage. These will be discussed this week at PDC.

The new features?

Entity Framework vNext will have the ability to generate the database from the EF model. In the bits that become available, all objects will be dropped from the database though, when refreshing the database from the model. As I understood, this should be fixed in the final .NET 4.0 release, if Entity Framework will be released with .NET.

Entity Framework vNext will support lazy loading. As in LINQ to SQL it’s a property and you can turn it on and off.

Entity Framework vNext will support TableValuedFunctions.

Entity Framework vNext will have support for less XML model, instead you decorate your classes with attributes.

You can find info on LINQ to SQL and stopping further development on it in this post and more in this post.

All in all I expected more from the Entity Framework Futures talk. There has been a lot of discussion about the Entity Framework and Tim just showed some v2 features. I expected more on what the grand plan was with Entity Framework. I guess this also involves “Oslo”, M and MEntity. We’ll just have to wait for more to come…

Oslo : Building textual DSLs

Dennis van der Stelt — Thu, 30 Oct 2008 19:48:43 GMT

This is the geek *** session Don Box mentioned. Chris Anderson and Giovanni Della-Libera are presenting, the entire Oslo team that’s here is inside this room.

module PDC

{

language Contacts

{

syntax Main = checked:Contact => checked;

syntax Contact =

"Contact" ":" a:Alias =>

Contact { Alias { a } };

"Contact" ":" a:Alias "-" n:PhoneNumber =>

Contact { Alias { a }, Phone {phone} };

token Alias = ('A'..'Z' | 'a'..'z')+;

token Digit = "0".."9";

token PhoneNumber = Digit#3 "-" Digit#3 "-" Digit#4;

interleave TokensIHate = " " | "\r" | "\n"+;

}

Tokenize is the first thing to do. The above can transform “Contact : dvdstelt - 425-555-1212”, and it removes weird characters. Chris and Gio than show how lists work, how the recursive results are flattened out, how to add comments and

mgx.exe is used to generated an mgx file.

mgx /r:contacts.mgx input.contacts will generate M language code. The mgx is just a plain .zip file, as said before in one of my posts.

mgx /r:contacts.mgx input.contacts /t:xaml for transformation to xaml

You can Integrate MGrammar into the CLR

Use MSBuild tasks, include the .mg file in your solution and setup the msbuild file (csproj)
Use the MgrammarCompiler, which is an in memory compiler
DynamicParser
IGraphBuilder

A cool example of some MGrammer was grammar code for MSI setup package. MSI is really complex to write, so Chris and Gio build MGrammar to build the MSI. But their MGrammer became so complex, that they wrote another MGrammer code library to generate the other MGrammer code to generate the MSI installer ‘code’. The final result is about 50 lines of MGrammer and 400 lines of C#, pretty maintainable I’d say.

To sum up, MGrammer is a language for creating textual DSLs. The specification will be released under OSP, as noted on many other weblogs.

You can build your own language right now! Download at http://msdn.microsoft.com/oslo/

“M” and MService

Dennis van der Stelt — Thu, 30 Oct 2008 19:02:25 GMT

I’ve been talking to people and perhaps here on the blog that during the Doug Purdy talk they showed a demo of MService where, with a few lines of code, a REST enabled WCF services with WF activities was created with only so few lines of actual code.

service Service

{

operation PhotoUpload(stream : Stream) : Text

{

.PostUriTemplate = "upload";

index : Text = invoke DateTime.Now.Ticks.ToString();

filename : Text = "d:\\demo\\photo\\" + index + ".jpg";

invoke MService.ServiceHelper.StoreInFile(stream, filename);

return index;

}

operation PhotoGet(index : Text) : Stream

{

.UriTemplate = "getphoto/{index}";

.ContentType = "image/jpeg";

filename : Text = "d:\\demo\\photo\\" + index + ".jpg";

return invoke File.OpenRead(filename);

}

endpoint HttpEndpoint

{

Binding = WebHttpBinding;

Address = "http://localhost:8080/service/";

}

Add breakpoints, post a photo or get one and the breakpoints are hit under debugging. You can see activities and endpoints in the locals window.

At the bottom you can see the endpoint defined. The first operation is PhotoUpload and it invokes code to store a file. Runtime this results in a WF activity storing the file on disc. The second operation is the get and it invokes a file read activity.

In the PhotoUpload operation you also see the invoke of DateTime.Now.Ticks.ToString(), which will result in a code-activity in WF, running the specified code.

This is just it, a REST enabled service for uploading, storing and retrieving images.

Remember that this is MService, including a WF/WCF runtime that understands the language ‘M’, hosted inside Dublin.

“Oslo” repositories and models

Dennis van der Stelt — Thu, 30 Oct 2008 16:54:14 GMT

Just saw Chris Sells show a session on some other expects of Oslo that wasn’t introduced yet.

It was again stated that the repository in Oslo is a normal SQL Server database. All your models are just SQL in the database and everything is designed for extensibility.

Some of the core features are:

Repository capabilities

Repository features are built on SQL Server
- Repository install also runs on useful features, e.g. replication and mirroring
Repository features are:
- Catalog
- Secure views
- Auditing
- Versioning
- Claims-based security, etc

The Oslo SDK provides tools to

Define new models : Intellipad, Visual Studio language services
Compile models : m.exe, msbuild build tasks
Deploy models : mx.exe

Again, once your models are in the database, it’s just plain SQL data.
Currently only SQL Server is supported, but of course the next logical step is XML and especially web services to put your models in the cloud!!!

Deployment

Packages can come from M files
packages can be exported from repository nodes

Security
Security is claims-based.

Identity becomes just one of several possible claims
Claims presented to authorize operations against resources

Repository tables keep track of claims, resources and operations

Triggers implemented on /t:Repository-generated views to check claims. Everything is stored in again in tables.
Views protect against direct access to tables

Domain-specific security containers

Use “folders” to partition data
Apps decide which data goes into what folder
Security checks happen on folder boundaries
Must call the field “Folder” for compiler to find it
Folder ID must exist in the Item.Folders table

Versioning

Data change synchronization

Between nodes using SQL Server Replication and Occasionally Connected Systems
Import/Export using SQL Server Change Tracking, e.g. repository <-> file system

Schema evolution

Extend M type and provide backwards compatibility for old clients w/ computed values
SQL Server Integration Services (SSIS) for data migration

"Oslo": Customizing and Extending the Visual Design Experience

Dennis van der Stelt — Wed, 29 Oct 2008 21:54:19 GMT

Together with Alex Thissen, Paul Gielens, Marco Stolk and Dries Marckmann we’ve been reflecting our thoughts on “M”. Right now we’re all at another Oslo talk about Quadrant.

Why “Quadrant”?

As more software becomes more model-driven, the volume of data in the system grows
We need a tool that lets people query, update, and visualize that data in ways that make sense for the task at hand.

What is “Quadrant”?

“Quadrant” is a tool for interacting with data
- Flexible, focused design surfaces
- Default experiences over arbitrary data
- Rich declarative customization
“Quadrant” is completely data-driven, every bit of data in SQL Server.

“Quadrant” is the tool to work with. You have a canvas where you can drag everything you’re working with on that canvas. Icons that are blue can be dragged out and placed on the canvas again to get a full view on that item again. That way you can drill down in all models. Everything of course in WPF and this provides a great visual experience, or at least this is the idea I get from looking at the screen.

Terminology and features in quadrant

Canvas
You can use the canvas to view the model. The model is loaded by Quadrant and you can drag models onto the canvas.
Repository Explorer
At the bottom-left corner you have the explorer from which you can select everything related to applications, models, workflows, activities, etc. Everything that is data and is represented as a model.
Shapes
Shapes are the squares on the canvas and are a model or a part of a model
Hyper icons
Hyper icons are the blue icons I talked about. They can be dragged out of the shape and become a new shape themselves.

Using Quadrant Takeaways

“Quadrant” connects people to data
Diverse data sets
Diverse interaction styles
Extensible
- Create new or extend existing models
- Create new or extend existing editing experiences

Customizing “Quadrant” Takeaways

Quadrant is a model-driven application
Customization via data stored in repository
View specification based on query/functional evaluation

Quadrant Architecture

The shell and surface has some core services like drag/drop, undo/redo, error handling, search, etc. The composition engine is getting data from a dataflow engine, giving queryable data, having target data, configuration and view state, which is all coming from M.

Where are we?

“Quadrant” is a flexible tool for interacting with diverse data
“Quadrant” uses the repository for both specification and state

Best PDC session so far : Lap around “Oslo”

Dennis van der Stelt — Tue, 28 Oct 2008 22:38:02 GMT

I’m at the “Lap around ‘Oslo’” talk together with Alex Thissen and Paul Gielens. This is by far the best session I’ve seen so far!

The talk began about models. We were looking at modeling and modeling domains, but what is a model? We have…

Drawings
Models used to communicate with others, for example DataFlow or Use Case. See UML as Sketch.
Model-Assisted
Models used to understand or manipulate code, for example StaticStructure or Sequence
Model-Driven
Models executed by runtimes directly, for example HTML, CSS, XAML, BPEL

According to Douglas Purdy, Don Box says we’re on a 30 year journey and we’re 15 years in. We had COM(+), .NET 1.0, Web Services, .NET 3.0 and now we’re entering the next phase. Oslo is the next level for a model-driven platform. We’ve been heading there via configuration, attributes and doing more and more declarative instead of typing everything out. A great example for declarative development is of course LINQ.

Why is this happening? Transparency (better understand your application), flexibility (add changes to your application faster) and productivity. We need models

So what is Oslo?
It is the platform for model-driven development. Microsoft will bring us Oslo with the following components:

“M”
The language for authoring models & DSLs
“Quadrant”
The tool for interacting with models & DSLs
Repository
The database for storing & sharing models, this will be SQL Server.

“M” gives you the modelling and textual DSLs. According to Douglas Purdy and to Don Box, this is going to be the next big thing. I could not agree more. I am SO excited about what I just saw. Take the example they’ve shown.

Module Microsoft.Samples

{

// MusicItem is the schema

type MusicItem

{

// Primary key

Id : Integer64 = AutoNumber();

Album : Text; // Album is constraint by type

Artist : Text;

// Rating is constraint and expression

Rating : Integer32 where value <= 3;

} where identity Id;

// * is 0..n multiplicity

MusicLibrary : MusicItem*;

}

The above declares a schema named “MusicItem” and a collection of those in a “MusicLibrary”. We compile this and than populate the result in the database.

// M compiler

// Repository is the database. When choosing -t:xml we generate XML

m.exe myfile.m /p:image -t:Repository

// Populating

mx.exe /i:myfile.mx /db:repository /ig /f

mx uses the compiled “binary” (this is a zip archive actually) and generates T-SQL.

create table [Microsoft.Samples].[MusicLibrary]

(

-- the rest

)

You can fill the database with the following

Module Microsoft.Samples

{

MusicLibrary

{

Album = "Slippery when wet",

Artitst = "Bon Jovi",

Rating = 3

{

Album = "Into the dark",

Artitst = "Europe",

Rating = 2

}

This creates two rows in the table MusicLibrary. But this is all the language “M”. How about a textual DSL? How’s this for coding:

"SomeAlbum" by "Led Zeppelin" is awesome!

"Back in Black" by "AC/DC" is so so.

"Bad" by "Michael Jackson" is terrible.

The above code can be transformed into the exact same code-block as above, where we filled the database with two records. How is this achieved? Take a look at the following code.

module Microsoft.Samples

{

import Language;

language MusicLibraryLanguage

{

syntax Main = s:Statement+ => MusicLibrary(valuesof(s){l

syntax Statement = al:Grammar.TextLiteral "by" ar:Gramar.TextLiteral "is" ?????

=> { Album {al}, Artist {ar}, Rating

@{(Classification["keyworkd"]} // colorize "awful"

token Rating1 = "terrible" | "awful";

token Rating2 = "so so";

token Rating3 = "awesome";

syntax Rating = Rating1 => 1 | Rating2 => 2 | Rating3 => 3;

interleave skippable = Base.Whitespace

}

I lost the code where it says “????”. The above code tells to look at by and is and takes the text there and parse it. It than looks at the rating and gives it an actual number. The Classification keyword makes the words “terrible” and “awful” become bold in the editor.

Now is this awesome or what? I’m so excited by this. This is one of the biggest steps in my history of developing software. You can now write code like

Give me a table called “Customers” with a primary key called “Id” and make it an integer with identity on, seeding from 1.

The best thing is, if you can think of a way to make that sentence shorter or more self-explaining, go ahead! Use MGrammer to define your own textual DSL.

MService
Another great demo was when they showed MService. With only a few lines of code (my battery ran flat, so I could not copy the code, but I photographed it and it will come in this blog!) they created a WCF service where they could upload an image and request it again, using a WF workflow. In about 38 lines of code, { and } on empty lines included!!!

Courtesy of Paul Gielens, I got the code from his weblog. The following starts a REST enabled WCF Service with a WF Writeline activity. Not a Console.Writeline, but a real WF activity.

module Service25

{

service Service

{

operation Echo(str : text) : Text

{

.UriTemplate = "echo/{str}";

WriteLine { Text = "Message : " + str }

return str;

}

Debugging
At first I thought this was an awesome code generator. But boy was I wrong. They showed debugging and hitting breakpoints inside the textual DSL!!! The stack and locals windows showed the WCF channels and WF activities active. Can you believe it? Probably not, you just have to watch the stream on Channel9.

I’m now going to follow Don Box, hold on for more!

Loving it, loving it, loving it, as Don Box would say!

CodeRush Xpress

Dennis van der Stelt — Tue, 28 Oct 2008 17:57:33 GMT

Mark Miller from DevExpress just announced CodeRush Xpress for C# developers, for free!!! In a partnership with Microsoft, DevExpress is making this tool available for Visual Studio. It’s a selection of CodeRush and Refactor! Pro features.

Refactor! Pro is one of my favorite tools available for Visual Studio. I haven’t really used CodeRush yet, but I will definitely install CodeRush Xpress.

Go get it here…

PDC 2008 Photos

Dennis van der Stelt — Tue, 28 Oct 2008 17:39:49 GMT

A lot of photos, many many more to come…

Most are Los Angeles, Santa Monica beach and other locations. PDC 2008 isn’t that interesting to look at! ;-)

http://flickr.com/photos/dvdstelt/sets/72157608454625991/