I found several SharePoint on Azure resources in the last couple days. Here they are for your (and my future) reference:
SharePoint 2013 on Windows Azure Infrastructure Services
A white paper by David Aiken and Dan Wesley. Synopsis: “This document provides guidance on how to deploy and operate a MIcrosoft SharePoint 2013 Server farm on Windows Azure Infrastructure Services.”
Installing SharePoint 2013 on Windows Azure Infrastructure Services
This is a tutorial continuation of the above white paper. Synopsis: “This tutorial contains the instructions for deploying a SharePoint 2013 farm on a set of Windows Azure Virtual Machines. The configuration consists of eight Virtual Machines. Each machine performs one of four roles, with duplication to ensure high availability”
SharePoint Deployment on Windows Azure Virtual Machines
A white paper from Microsoft (unattributed author). Synopsis: “This paper provides guidance about the benefits of Windows Azure Virtual Machines and explains how to deploy SharePoint Server 2010 on Windows Azure Virtual Machines.”
SharePoint Server 2013 Trial VM
You’ll need to find this pre-configured SharePoint 2013 VM in the Azure Gallery. Synopsis: “Microsoft SharePoint Server 2013 Trial on Windows Server 2012 Datacenter. Virtual Machines created with this trial image will expire on March 17, 2014. This image includes a complete installation of SharePoint Server 2013. Some SharePoint Server 2013 components require additional setup and configuration. You can set-up Active Directory and SQL Server required for your SharePoint farm by provisioning additional virtual machines. Minimum recommended virtual machine size for this image is Large. To evaluate the advanced capabilities of SharePoint Server 2013, we recommend that you use a virtual machine size of Extra Large.”
SharePoint Developer Virtual Machine in Azure Gallery
There is also a pre-configured developer VM geared toward SharePoint 2013 development. Synopsis: “The Visual Studio 2013 image is an exclusive offer for MSDN subscribers and provides the capability to quickly provision a development environment for Web/SQL development and for SharePoint 2013 development on an Azure Virtual machine. The image is available for MSDN Professional, Premium and Ultimate subscribers. You need to choose an image that corresponds to your subscription level. Visual Studio will check your subscription level during sign in and will only allow you to proceed if your subscription level matches the VS SKU on the image.
- Visual Studio 2013 Professional|Premium|Ultimate
- Windows Azure SDK for .NET 2.2
- SQL Server 2012 SP1 Developer Edition
- SharePoint 2013 Trial
- Scripts to provision SharePoint 2013 and SQL Server
The scripts on the image allow you to configure the virtual machine for either SQL, Web development or for SharePoint development. The virtual machine can be provisioned through the portal or through PowerShell and PowerShell Remoting. This tutorial will guide you through both options.”
If you’re going after a SharePoint 2013 developer certification, you know one of the exams you must pass is for ASP .NET MVC (70-486). MVC comes into play when you start creating Autohosted or Provider Hosted SharePoint Apps running on Azure. However, they default Autohosted App runs Web forms, not MVC.
MVC is important, just not important enough to warrant baking into the project template *snark*. Just kidding. I don’t know why it’s not built into the template by default, but I can tell you the story has gotten much better.
*Update: 8/22/2013 – I just realized that Microsoft added support for MVC in SharePoint Apps out of the box in the Visual Studio 2013 preview. This post is still relevant for Visual Studio 2012
Step 1) Create your Autohosted SharePoint App. Be sure to set the .NET Framework drop down to 4.
Step 2) Add an ASP .NET MVC project to your solution. Again, make sure .NET Framework 4 is selected. I’ve tested these instructions with the Internet, HotTowel, and Durandal flavors of MVC, but I think the others should all work as well. Web API may prove very useful, but I haven’t tested it yet.
Step 3) In your application project, set your new MVC project as the Web Project. and F5 to deploy.
You can then remove the original web project that Visual Studio created for you (in my example it was called SP_MVCWeb). Since the app will deploy without doing this, it’s not an official step, thus my 3 step claim remains accurate.
Thanks to everyone that came out to the Heartland Region SharePoint Conference. I had a great time and the feedback was tremendous.
You can find the slides and demo code in my SkyDrive folder here: http://sdrv.ms/YA1A8O
You don’t see a lot of SharePoint poetry out there and there’s a reason for that – it would be terrible. However, some of you may enjoy a bit of terrible niche poetry on a Monday morning. For you yet-to-be-institutionalized folk out there I’m posting this piece that I wrote for a coworker. I run my company’s internal SharePoint Group and Mike was our featured speaker last week. Since our meeting invitations go out through the company news letter, I try to keep them from being too bland.
Michael McNett is McNuts about SharePoint.
He’s a fan of Fast Search and a Friend to refining.
Content types make him cry like he’s christened a son.
Extranets excite him and his eyes you’d see shining
If integrating InfoPath is the job to be done.
Populating profile properties is Mike’s thrill.
He loves publishing the perfect profile post.
His RoadMap is no ruse. If you need things done right,
It’s the best way to ensure that your timeline is tight.
BTW, you can find Mike’s through his blog,http://mmcnett.wordpress.com/, on LinkedIn or twitter (@CIO_Mike)