Archive for the ‘SharePoint 2013’ Category
Creating virtual machines with Azure is a great way of standing up test servers, especially for SharePoint where the installation can be long.
You can create a SharePoint Server 2014 trial server from Azure by first selecting “From Gallery”:
And then select the “SharePoint Server 2013 Trial”
The problem with this is that SharePoint is already installed for a farm installation and therefore cannot be installed as a standalone server. As the description provided by Microsoft states, you will need to create another virtual machine for SQL Server and possibly another for a domain controller with Active Directory.
To circumvent this issue you can:
- Create the VM using the gallery in Azure as shown above
- Install SQL Server Express 2012 on the newly create VM
- Create a new farm using the New-SPConfigurationDatabase PowerShell command
- Run the SharePoint Products Configurations Wizard and join the farm you’ve just created.
The last three steps are described in this excellent blog article: http://blogs.msdn.com/b/suhasaraos/archive/2013/04/06/installing-sharepoint-2013-on-a-single-server-without-a-domain-controller-and-using-sql-server-express.aspx
All the SharePoint 2014 Conference sessions are now available on Channel 9 for free viewing.
This is a great move by Microsoft.
You can watch the keynote from the SharePoint 2014 Conference in Las Vegas here: http://channel9.msdn.com/Events/SharePoint-Conference/2014/KEY01
Bill Clinton’s talk is not included in this recording, but it’s available on YouTube here:
Bill Clinton talks about how technology has supported world health, food, charity and disaster recovery. Worth a listen. Here’s the book by E.O.Wilson mentioned in this talk: http://www.amazon.com/Social-Conquest-Earth-Edward-Wilson/dp/0871403633
The clear message from Microsoft for SharePoint 2013 development is a move to the app model. Here’s an introduction: http://msdn.microsoft.com/en-us/library/jj164084.aspx. SharePoint 2013 apps moves your code assemblies out of the SharePoint platform and into separate web applications. There are two reason for this:
1. A requirement for a more stable SharePoint platform. If you’re running SharePoint across your organization you don’t want badly written applications impacting reliability.
2. In Office 365 you can only add assemblies in sandboxed solutions. However, because of the very constrained subset of the SharePoint API available to such solutions their functionality is limited. Now, Office 365 will use functionality provided by SharePoint apps.
The move to SharePoint 2013 brings SharePoint 2013 developers fully back into the ASP.NET development fold. In particular, MVC with Razor greatly simplifies web application development. You will be using the SharePoint Client Object Model to access SharePoint objects from your app.
Here are some links that help you get started with building SharePoint 2013 apps:
- How to: Create high-trust apps for SharePoint 2013 using the server-to-server protocol: http://msdn.microsoft.com/en-us/library/office/apps/fp179901. Essential for building on-premise SharePoint 2013 apps.
- Building ASP.NET MVC Based SharePoint Cloud Apps: http://www.ilovesharepoint.com/2012/07/building-aspnet-mvc-based-sharepoint.html. A number of steps in this guide are automatically performed with Visual Studio 2012 released version.
- ASP.NET MVC 4: http://www.asp.net/mvc/tutorials/mvc-4. An excellent introduction to get you up to speed with ASP.NET MVC with Razor.
SharePoint 2013 is now at RTM and available for preview. It’s disappointing that a default, single server install has issues that occur often and predictably, even on a clean Windows 2012 Server install. Of course, we expect errors and problems, especially with early release software. However, the default install should just work at this stage of the product lifecycle.
There are several blog posts that describe how to correct these issues. This is one of the better ones: http://squidpip.com/blog/sharepoint-2013-preview-configuration/.
Also, there’s a deployment guide from Microsoft which can be found here: http://www.microsoft.com/en-us/download/details.aspx?id=30384 . Be prepared though, it’s 675 pages long!
For some time now deploying assemblies in the “bin” folder in virtual folders under inetpub has been frowned on in SharePoint. Well, it’s now deprecated in SharePoint 2013 and an attempt to do this will cause Install-SPSolution to fail.
If you really, really, have to you can use the -FullTrustBinDeployment parameter to allow this behavior. However, you should really look to deploy assemblies to the GAC.