C:\Users\tim\Downloads\aspnet_regsqlazure>aspnet_regsqlazure
Execution failed:
You must specify a Server, Login ID and Password.

Don’t even think about –? or –h.  I went h.  Likely the options will be similar to aspnet_regsvr, but for the geek-at-heart, source code is included (see below).

I used the following

C:\Users\tim\Downloads\aspnet_regsqlazure>aspnet_regsqlazure -xxxxxxxx.database.windows.net -U tim -P xxxxxxx -d xxxxx -A all

Note that you will see

Cannot grant, deny, or revoke permissions to sa, dbo, entity owner, information_schema, sys, or yourself.

It’s ok.

——

If you see this error (HTTP Error 403.14) while getting started with Azure, it is likely that Directory Browsing is not enabled.  Go ahead and fire up IIS Manager and click on the Directory Browsing icon under IIS.  You should see something like this:

Click enable, restart the server and re-run your code.  If all goes well, you’ll be led to a directory view of your dev instance.

Mmmm.  Nice.  Except of course, that code did not start from Line 1 in my codebase…  but this is already much improved.

We can make it nicer using custom CSS, but WordPress charges for that.

namespace

<UserControl x:Class="AppHelper.LoginCtrl"
             xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
             xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
             mc:Ignorable="d"
             d:DesignHeight="300" d:DesignWidth="300">
    <Grid>
    </Grid>
</UserControl>

and this:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Windows;
using System.Windows.Controls;
using System.Windows.Data;
using System.Windows.Documents;
using System.Windows.Input;
using System.Windows.Media;
using System.Windows.Media.Imaging;
using System.Windows.Navigation;
using System.Windows.Shapes;

namespace AppHelper
{
    /// <summary>
    /// Interaction logic for LoginCtrl.xaml
    /// </summary>
    public partial class LoginCtrl : UserControl
    {
        public LoginCtrl()
        {
            InitializeComponent();
        }
    }
}

Sweet.

MEF is now on Preview 9 and slated for final release sometime in the near future part of .NET 4. Unfortunately, while well-written examples exist, they mostly seem to be based on Previews which have become out of date. The example I went through essentially follows Robert Muehsig’s well-written Hello MEF, with updated code.

Here’s the idea. First, I created an interface in the HelloService project. This be referenced by your App project as well as any extensions.

namespace HelloService
{
    public interface IHelloService
    {
        string GetHelloMessage();
    }
}

Next, in two additional projects, HelloService.Chinese and HelloService.English, I created the following:

using System.ComponentModel.Composition;

namespace HelloService.Chinese
{
    [Export(typeof(IHelloService))]
    public class ChineseHelloService : IHelloService
    {
        public string GetHelloMessage()
        {
            return "你好世界";
        }
    }
}

and

using System.ComponentModel.Composition;

namespace HelloService.English
{
    [Export(typeof(IHelloService))]
    public class EnglishHelloService : IHelloService
    {
        public string GetHelloMessage()
        {
            return "Hello World";
        }
    }
}

Make sure to add System.ComponentModel.Composition (and HelloService) in these two projects. This lets “Export” work. This takes care of the extensions.

I defined the host in a new project called HelloAppBase. In this case, MEF will check both my executing assembly (called using System.Reflection) and the “Plugins” directory. It is apparently also possible to monitor changes in the directory and monitor changes in realtime. The sweetest part of all this is the ImportMany above the List. It works so magically that it scares me… just a bit.

    public class HelloProgram
    {
        [ImportMany(typeof(IHelloService))]
        public List Services { get; set; }

        public HelloProgram()
        {
            var directory = "Plugins";
            if (!Directory.Exists(directory))
            {
                Directory.CreateDirectory(directory);
            }

            var catalog = new AggregateCatalog(
                new AssemblyCatalog(Assembly.GetExecutingAssembly()),
                new DirectoryCatalog(directory));

            var container = new CompositionContainer(catalog);
            container.ComposeParts(this);
        }

        public void WriteHelloGreetings()
        {
            Console.WriteLine();
            Console.WriteLine("Writing Greetings...");

            foreach (IHelloService svc in Services)
            {
                Console.WriteLine(svc.GetHelloMessage());
            }

            Console.WriteLine("...powered by MEF");
        }
    }

Very clean. I like it.

Finally, create a Console application that calls HelloProgram. In Visual Studio, I created a Plugins directory within the Project and placed the two extensions (HelloService.Chinese.dll and HelloService.English.dll). Make sure the Properties for these are Content, Copy if newer. You can also drop them in by hand into the executing directory, but this saves some time.

using HelloAppBase;

namespace HelloConsole
{
    class Program
    {
        static void Main(string[] args)
        {
            HelloProgram program = new HelloProgram();
            program.WriteHelloGreetings();

            Console.ReadLine();
        }
    }
}

Yeehaw.

Update:
After drafting this post, I did a search and found Derik Whittaker’s Kick Start Example. Though built for Preview 8, everything looks good and should work.

• Cocoa – cocoa-oauth2 from Lee Byron works at Facebook, so this ought to be a solid reference. The project has no licensing information.
• Ruby – OAuth2 Gem from Intridea and Michael Bleigh. Built for the new Facebook Graph API, it carries an unrestrictive license. Their blog post summarizes installation and usage. Michael writes “OAuth 2.0 is an almost entirely different beast than 1.0a and they share so little functionality…”

Note that there is a Python library called python-oauth2 from simplegeo. Do not be confused. This is not OAuth 2.0. It is a fork from Leah Culver’s oauth.py. I found nothing in CodePlex or CodeProject.

My favorite OAuth client library is Andrew Arnott’s DotNetOpenAuth – though it is rather weighty since it includes both client and provider as well as OpenID. In a recent tweet, Arnott claimed “oauth 2.0 support is slated for DotNetOpenAuth 3.5″ (currently 3.4.3). I hope it comes soon! If you have any leads, please post below.

Update:
I found an ASP.NET Facebook-OAuth2 sample by Osznaps based on earlier work on Twitter OAuth. “The really great news is that OAuth 2.0 is super simple to use.”