The Windows Home Server “Vail” preview is here. There have been lots of in-depth technical reviews of the new and updated bits in Vail, which is not surprising given how anticipated the new version has been.

The new functionality and improvements to the basic Windows Home Server infrastructure look great. I’m especially pleased that DE v2 now operates at a level below the file system; it’s going to be much more robust. Bye-bye file conflicts!

Of course, what really piques my interest in Vail is the new Software Development Kit. We’ve already seen a few previews and guides from the community on the SDK in Vail.

I’ve talked about what I think of the WHS v1 SDK in other places, suffice to say that it’s pretty rudimentary. There aren’t lots of bells and whistles in the plug-in model; really, you just provide WHS v1 with a WinForms control and you’re responsible for handling everything after the initial load.

So, after having played with the Vail SDK, what do I think? If I had to use two words, they’d be pure awesome.

My top 10 list of awesomeness:

  1. Magic WCF connectivity between Add-Ins, the server, and clients
  2. Magic INotifyPropertyChanged data binding for lists of business objects
  3. Core Add-Ins in Vail use the same Providers and SDK components as your code
  4. Core Add-Ins in Vail can be extended by adding your own tabs
  5. Core providers in Vail can be replaced entirely by your code
  6. Access to the Windows Server 2008 R2 SDK
  7. Remote Access web application can be extended
  8. Client-side Launchpad can be extended
  9. Health monitoring is a first-class citizen of the SDK
  10. Documentation

The last point is especially important; it took a long time for the community (and Microsoft) to develop decent documentation for WHS v1 Add-In development. Now, even the beta Vail SDK ships with proper documentation for all components and an end-to-end walkthrough of creating an Add-In from scratch; looks like I won’t have to go through a massive screenshot exercise this time!

I’m very excited about the SDK, as you can probably tell. Microsoft have put a lot of effort and thought into making Vail as extensible as possible, and it’s going to help 3rd-party developers make some really cool new toys for Windows Home Server.

There’s going to be a learning curve, of course. WHS v1 Add-Ins don’t “just work” in Vail, so you’re going to have to do quite a lot of conversion and re-architecture. But trust me, it’s going to be worth it when you see just how clean everything becomes in Vail.

posted on Friday, May 07, 2010 10:16 AM | Filed Under [ Windows Home Server Development Microsoft ]

Comments

Gravatar
# re: Windows Home Server “Vail” Software Development Kit (John @ 5/24/2010 4:27 AM)

Hey Sam very nice resource here, I've read up on quite a bit and got my Vail preview installed. Im going through the SDK now and setting up my environment but stumbled across something unusual. There are some templates provided which I have copied into my VS templates folder, when I open up visual studio all of the template show under new project/my templates except one; Provider Object Model. As I understand it this is a critical component if you wish to separate the the business logic of an addin and provide extensible features. Do you have any idea why this template refuses to show?
 
Gravatar
# re: Windows Home Server “Vail” Software Development Kit (Sam Wood @ 6/9/2010 1:02 PM)

Hi John,

No, not sure why it's not showing up. Which version of Visual Studio are you using?
 
Gravatar
# re: Windows Home Server “Vail” Software Development Kit (John @ 7/28/2010 7:45 AM)

Hey sorry for the late response; I was a bit busy and had trouble viewing your comment system. I'm using VS 2008 Pro with SP1 I also have VS 2010 Pro if needed. There is something else I've noticed about the SDK the provider template references "ProviderObjectModel" however I can't find this library anywhere on my server.
 
Gravatar
# re: Windows Home Server “Vail” Software Development Kit (John @ 8/18/2010 6:34 AM)

Never figured out why the template wasn't working but I did realise what the project was referencing lol. All sorted.

Post Comment

Title *
Name *
Email
Url
Comment *  
Remember me
Please add 6 and 2 and type the answer here:

Search

Site Sections

Recent Posts

Archives

Post Categories

WHS Add-In Tutorial

WHS Blogs

WHS Development