Sunday, August 31, 2014

Getting to know DocumentDB - Part 2

For Signing up for DocumentDB read here:

Getting to know Document DB - Part 1 here:

In Part 1 we found that we need to install Microsoft Azure DB Client Library.

In this post we will install the client library as well as look at the Microsoft created sample which is perhaps the best way to look at the details of DocumentDB.

Installing Microsoft Azure DocumentDB Client Library
Client Applications connect to Azure DocumentDB service using Client Library.
In order to install Microsoft Azure DocumentDB Client Library you need to run the command:
PM> Install-Package Microsoft.Azure.Documents.Client-Pre

PM is the Package Manager Console. If you do not know how to get to the console read here.

  •  Launch Visual Studio 2013 Express for Web Update 3. -Run as administrator
Make sure you have the NuGet properly installed. If not get it from the Gallery Tools | Extensions and Updates...
  • Click Open the Packet Manager Console

Type in the install script mentioned above and you will get an error message as there is no solution yet.
  • Download the C# Sample from here:
Download, extract and open it in Visual Studio.

When you build you may get some 12 error messages.
Now in the Package Manager Console run the Install again as shown
PM> Install-Package Microsoft.Azure.Documents.Client -Pre
Attempting to resolve dependency 'Newtonsoft.Json (= 4.5.11)'.
Installing 'Microsoft.Azure.Documents.Client 0.9.0-preview'.
You are downloading Microsoft.Azure.Documents.Client from Microsoft, the license agreement to which is available at Check the package for additional dependencies, which may come with their own license agreement(s). Your use of the package and dependencies constitutes your acceptance of their license agreements. If you do not accept the license agreement(s), then delete the relevant components from your device.
Successfully installed 'Microsoft.Azure.Documents.Client 0.9.0-preview'.
Adding 'Microsoft.Azure.Documents.Client 0.9.0-preview' to DocumentDB.Samples.DatabaseManagement.
Successfully added 'Microsoft.Azure.Documents.Client 0.9.0-preview' to DocumentDB.Samples.DatabaseManagement.
Build the project again:
Now you are still showing six errors.

Some of these are related to missing references:

I guess the latest SDK (Microsoft Azure SDK 2.4)  is needed.
Go to notifications area and install the latest SDK.

Download the SDK

Run the SDK
Web Platform Instlaler takes over.

Now you are ready to install MSFT Azure SDK for .NET (VS2013) -2.4
Click Install.

Once you download the Microsoft Azure SDK, the errors go away and the build succeeds.

We look at the details of the project in the next post here.

Saturday, August 30, 2014

Azure SQL Databases going to cost even lower after September 2014

Another name is price war and the battle is on going on all fronts. There has been news on the
internet regarding Microsoft's pricewar with Amazon and Google vis-a vis its cloud offerings.

Although Cloud business (the thriving one) is only a small part of Microsoft right now it makes sense to make it invincible.

Old prices and service tiers here:

Come September the price for Azure SQL Databases will be  slashed.
Reduced pricing and enhanced SLA available in September. Read here:

The new pricing is as in the following image from the above site:

Note that a new S0(S-Zero) performance level has been added in the Standard tier meant for lower-cost entry point.

Tuesday, August 26, 2014

Updating the Windows* Phone 8.1 Update

In my previous post here I ranted on the Nokia Lumia Icon I bought from Verizon.

In this post I will describe what else has happened since.

I have not been able to find anything about Nokia Lumia Icon alias Nokia Lumia 929. I have posted the question to the Windows Phone Central.

When I bought the Nokia Icon phone from Verizon the OS version was 8.0.10521.155

Then I installed Windows 8.1 Preview for developers and this version was 8.10.12397.895

There has been other updates. The following were the updates I agreed to install on the same day.
8.10.14147.180;  8.10.12400.899; and 8.10.14157.200

The update 8.10.14147 appears the latest according to:

Is it? I have 8.10.14157.200.

The last updates took quite a bit of time that included updating some 20 files.

This is OK. I am still puzzled whether I am still in the 'Preview Park' or the 'RTM'. Another frustrating thing with the updates is that no reason is given for these updates. Things need to be transparent.

At least with Visual Studio updates, you do get some idea of what has been updated.