{"id":157,"date":"2008-12-14T20:12:12","date_gmt":"2008-12-14T19:12:12","guid":{"rendered":"http:\/\/www.leading-edge-dev.de\/?p=157"},"modified":"2010-07-10T10:56:50","modified_gmt":"2010-07-10T09:56:50","slug":"live-framework-ctp-4-net-loe-and-data-basics","status":"publish","type":"post","link":"https:\/\/www.minddriven.de\/index.php\/technology\/microsoft\/cloud-computing\/live-services\/live-framework-ctp-4-net-loe-and-data-basics","title":{"rendered":"Live Framework CTP #4 – .NET: LOE and data basics"},"content":{"rendered":"

Instead of creating new Silverlight applications, which run in your mesh and use the data, you can furthermore mesh-enable<\/em> your existing .NET applications or create new mesh-enabled .NET applications from scratch. That’s pretty easy and in the following post I will show you some basics…<\/p>\n

The Live Operating Environment (LOE)<\/h2>\n

First there is the Live Operating Environment<\/strong>, being the center point of all your operations to the mesh. With an object of type LiveOperatingEnvironment<\/code> you can connect to your online mesh or to your local mesh storage sync or async and perform any operation you want. But that’s just the developer’s point of view. In fact, the LOE (every instance of it) is an agent component<\/strong>, responsible for providing an efficient cache and for background synchronization of data on your device to other devices (other instances of the LOE on those devices) in your mesh, including the „special“ LOE in the cloud. Running an LOE means exposing data through a RESTful interface at port 2048 of your machine – one could check the presence of this and either connect locally or to the cloud.<\/p>\n

Connecting to your online\/cloud LOE means that you have to provide your credentials on connect, whereas you can connect locally without those. I like to work on my local storage, it’s fast and safe. But there are some limitations (at the moment?) there. Due to the lack of file synchronization, files as data entries are not available from the local storage, so you have to connect to your online LOE instead. Furthermore you only get your local device in the Devices<\/code> collection of your LOE and it’s not possible to have a look at your contacts and profiles\u00a0for instance. What I expected first or want to have for the „final“ version of the Live Framework: just one connection method, which takes local data if it’s available and instead connects to the cloud LOE. It should be no problem, because the various LOEs (loal, cloud) are taking responsibility over synchronization… or have I forgotten to consider something?<\/p>\n

Well, let’s take a look to connecting to your (online) LOE. Just create an instance of LiveOperatingEnvironment<\/code> and connect via the Connect()<\/code> method (local LOE: use ConnectLocally()<\/code> instead). You have to pass your credentials as a parameter, which could come from a secure source or from user input:<\/p>\n

var creds = new NetworkCredential(\"username\", \"password\", \"https:\/\/user-ctp.windows.net\");\r\nvar loe = new LiveOperatingEnvironment();\r\n\r\nloe.Connect(creds);<\/pre>\n
https:\/\/user-ctp.windows.net<\/code> is the fixed base URI when connecting to your cloud LOE. After you’ve been connected, you get access to your mesh items (shown before<\/a>) and can start meshing \ud83d\ude42<\/p>\n
Mesh Objects, Data Feeds and Data Entries<\/h2>\n
A mesh object<\/em> is a container for concrete data in your mesh. There are several types of mesh objects and you are allowed to create your own application specific types, which your applications can work with. Mesh objects can be files, folders, applications, custom objects etc.. You have access to the mesh objects via loe.Mesh.MeshObjects.Entries<\/code> and have the possibililty to easily iterate over them in this way.<\/p>\n
Every mesh object consists of DataFeeds<\/code>, Members<\/code>, Mappings<\/code> and News<\/code>, as stated before<\/a>. Interesting at this point are the data feeds. Those are further containers for the real<\/em> data entries. Why this abstraction? Over data feeds you can group your data together, separating logically distinct data. Every DataFeed<\/code> object finally contains a DataEntries<\/code> collection, which gives you access to the underlying data and information about that. Note: there is no obvious possibility to store hierarchical data entries<\/strong> at the moment. There is one level of data entries and a data entry can’t contain other data entries. So that’s a drawback at this point and I don’t like\/understand it much. The solution<\/a> for that is: every data entry contains a parent ID and over that you can identify top level data entries and those, who are child entries of another data entry. But that’s not a good solution, isn’t it? Hopefully there will be done some work on that…<\/p>\n
Well, a nice little .NET console application would be to show us the titles of all mesh objects, of their data feeds and data entries in there. That’s no problem and leads to the following little program:<\/p>\n
var creds = new NetworkCredential(\"username\", \"password\", \"https:\/\/user-ctp.windows.net\");\r\nvar loe = new LiveOperatingEnvironment();\r\nloe.Connect(creds);\r\nif (loe.IsRunning())\r\n{\r\n    foreach (var meshobj in loe.Mesh.MeshObjects.Entries)\r\n    {\r\n        Console.WriteLine(\"- \" + meshobj.Resource.Title);\r\n        foreach (var feed in meshobj.DataFeeds.Entries)\r\n        {\r\n            Console.WriteLine(\"  + \" + feed.Resource.Title);\r\n            foreach (var entry in feed.DataEntries.Entries)\r\n                Console.WriteLine(\"    * \" + entry.Resource.Title);\r\n        }\r\n    }\r\n}\r\nConsole.ReadLine();<\/pre>\n
Create, Update, Delete<\/h2>\n
The creation, update and delete of all the three entities MeshObject<\/code>, DataFeed<\/code> and DataEntry<\/code> is made really easy. Just call the Add()<\/code> and Remove()<\/code> methods of the particular collections. The rest is done automatically by the Live Framework. The update process isn’t problematic, too. Just change your entity and then make sure to call the Update()<\/code> method of this entity. Because everything in your Live Operating Environment has LiveItem<\/strong> as base type, you have an integrated and consistent CRUD process.<\/p>\n
Little example<\/h2>\n
The following screenshot shows a little WinForms application, that connects to my mesh and over which I can perform the CRUD process on my mesh entities. Further on I can navigate through my mesh and if I got images as data entries, those are downloaded automatically as media resource stream and then shown up at the picture box on the right. In the screen below is shown the (IKEA-powered \ud83d\ude09 ) couch corner of my little apartment…<\/p>\n
\"Live<\/p>\n
In upcoming blog posts I want to show you more information about handling data entries, media resources and hierarchical data. So stay tuned \ud83d\ude42<\/p>\n
\"kick<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Instead of creating new Silverlight applications, which run in your mesh and use the data, you can furthermore mesh-enable your existing .NET applications or create new mesh-enabled .NET applications from scratch. That’s pretty easy and in the following post I will show you some basics… The Live Operating Environment (LOE) First there is the Live … Live Framework CTP #4 – .NET: LOE and data basics<\/span> weiterlesen<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[87,89,71],"tags":[96,99,100,55,90,97,98],"class_list":["post-157","post","type-post","status-publish","format-standard","hentry","category-live-framework","category-live-mesh","category-live-services","tag-crud","tag-data-entries","tag-data-feeds","tag-live--framework","tag-live-framework-ctp","tag-live-operating-environment","tag-mesh-objects"],"_links":{"self":[{"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/posts\/157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/comments?post=157"}],"version-history":[{"count":12,"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/posts\/157\/revisions"}],"predecessor-version":[{"id":950,"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/posts\/157\/revisions\/950"}],"wp:attachment":[{"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/media?parent=157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/categories?post=157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.minddriven.de\/index.php\/wp-json\/wp\/v2\/tags?post=157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}