One of the things the Live Framework has to offer is a Local Live Operating Environment you can connect to so that you can Offline Enable your Live Framework Enabled Desktop Applications. I found the process of getting it to work a little tricky (especially since I was running Win7 Beta; I’ll explain down further) so I’ve decided to write up a summary of my experience to help anyone else interested.
This was written using the Live Framework CTP.
Connecting to the Live Operating Environment
The “Live Operating Environment” is the main service that is hosted in the cloud by Microsoft. To connect to it and use it you are required to be connected to the Internet.
Basically to connect to the Live Operating Environment you need to prompt the user for their Windows Live ID and Password. Below is a very simple example of what is needed to create an instance of the LiveOperatingEnvironment object in C# and connect to the Live Operating Environment server.
var credentials = new System.Net.NetworkCredentials(windowsLiveID, password); var LOE = new LiveOperatingEnvironment(); LOE.Connect(credentials);
I you haven’t really looked in to how this works, you can look at the ConnectCloud method of the Login.xaml.cs file of the Project Manager sample code within the Live Framework CTP SDK.
Connecting to the Local Live Operating Environment
Now, to connect to the **Local **Live Operating Environment instead, you basically just call the LiveOperatingEnvironment.ConnectLocal() method instead of the Connect() method shown above. Also, another big difference is you don’t need to prompt the user for their Windows Live ID and Password, since the Local Live Operating Environment handles all the authentication for you.
var LOE = new LiveOperatingEnvironment(); LOE.ConnectLocal();
This also has the benefit of only requiring the user to type in their Windows Live ID and Password once when they login with the Live Framework Client; which can actually save their password and auto log them in when they login to Windows.
Mesh Client or Live Framework Client? What's the difference?
When you go to http://mesh.com, login, and click “Add Device” so you can Sync files with Mesh Folders, it has you install the Mesh Client. This install does not contain the Local Live Operating Environment you need when programming against the Live Framework SDK.
When you go to http://developer.mesh-ctp.com, login, and click “Add Device” so you can Sync files with the “dev” version of Mesh, it has you install the Live Framework Client. This is in fact the install you want that contains the Local Live Operating Environment.
Beware the Mesh Client and Live Framework Client don't play well together
Actually, the latest update (April CTP) to the Live Framework Client does install and work correctly along-side the Mesh Client.AND, it now works on the Windows 7 Beta.
There is a known issue of running the Live Framework Client and Mesh Client on the same machine; they simply don’t work as installed out of the box. You need to perform a little registry edit to fix the issue. It sounds bad, but it is actually quite painless.
Here’s instructions on how to get the Mesh Client and Live Framework Client to run Side By Side:
- Uninstall Live Framework Client.
- Install Mesh Client Beta from http://mesh.com
- Add the following registry item: HKCU\Software\Microsoft\Live Framework Client\AllowSxS = 1 (DWORD)
- Install Live Framework Client from http://developer.mesh-ctp.com
The original posting of these instructions and a little more detail about them can be found here:
Current Live Framework Client does not work on the Windows 7 Beta
One thing to note before you start trying to develop against the Local Live Operating Environment is it does NOT run correctly on the Windows 7 Beta. In order to develop for it and use it you’ll need to install it on Windows Vista (or presumably Windows XP).