SharePoint 2013 Preview introduces a number of new elements and additional considerations for multi tenancy deployments. This article is intended as a companion to my Rational Guide to Multi Tenancy with SharePoint 2010 article series and will cover what’s new and changed in this release with respect to configuration and functionality. It is assumed you are familiar with the material in the article series.
Using PowerShell, we’re going to walk through handling a Choice field in a list. Specifically, this is a calendar list using the Category field. This may come in handy if you want to automate changing the values from another data source that BCS can’t connect to, or is too much work to get it to connect. I always prefer using SharePoint’s features, but sometimes we need to stretch it to make it work.
I am extremely interested in the new SharePoint 2013 App model so I have been doing a lot with them lately. The latest thing I was trying was building a SharePoint-hosted Client Web Part. I have found that there is not a lot of information out there yet on how to use these so I wanted to share some of the things I ran into. This post on MSDN is good to help you get started with the setup of your app. Hopefully this info will help you get started. This post assumes you have installed Visual Studio 2012 RC as well as the SharePoint development tools.
This white paper provides an overview of Dell’s SharePoint Infrastructure Optimization solution. Details of the solution stack, which includes components of AvePoint’s DocAve Software Platform and Dell hardware components, are discussed along with the set of functional and performance tests that were used to verify the solution.
‘Governance Rules!’ is an exciting new monthly programme, exclusive to The European SharePoint Community, delivered by Christian Buckley, SharePoint MVP and internationally recognized author and speaker. In this programme, Christian will be touching on a different aspect of SharePoint governance each month – including the governance impacts and influences around migrations, permissions management, reporting, risk management, the cloud, and social platforms.
It is an exciting time for all of us in the SharePoint community. SharePoint 2013 is definitely one of the most anticipated Microsoft releases and many people have been waiting patiently to get their feet wet. Last week’s public beta marks a major milestone in the SharePoint 2013 journey. Whether or not your organization plans to upgrade to the new version immediately after the RTM – whenever that may be– the time is right to start preparing for it. Learning about ways to upgrade to SharePoint 2013 and what has changed in the upgrade process is an important step in getting yourself ready.
Microsoft is very excited for the new release of SharePoint 2013 and the buzz around the new features that it is adding to search. One of these main features that your users will be able to take advantage of is document preview in your search results.
SharePoint 2013 will, without a doubt, be a huge success for Microsoft. The SharePoint platform has come a long way and SharePoint 2013 (code named SP15) is another leap forward. Search is one of the areas where Microsoft has, once again, made huge investments and the new functionality is astounding.
I was a guest speaker on a general SharePoint Security Webcast today, which was great fun. On the agenda was security of SharePoint relating to mobile devices. Unfortunately, the session did not manage to get into that topic, and I was so keen to talk about it. To counter, I’ve provided an article written today which talks about how personal devices as part of Consumerization have impacted SharePoint, some features available to mobile users, what implications are there in terms of security and finally a look at what Support needs to address.
SharePoint 2013 introduces a new mechanism for custom code deployment known as “Apps”. Mostly targeted at online solutions, the purpose of the App model is to overcome the severe limitations of the 2010 isolated execution model (also known as the “Sandbox”) and provide developers with a way to run rich web applications in SharePoint without negatively impacting the underlying infrastructure. Much has already been made about this new model and a lot more will be written about it over the coming year as 2013 gets released and adoption spreads. Before we get too far off the beaten track into a debate about whether or not developers should or should not be using the new App model, it’s helpful to first understand why Microsoft chose this path and what it really means for both new application developers coming onto the platform and existing developers who need to support the next release.
