1 to 10 of 48
Sort by

Blog Entry
SharePoint 2013 Migration

In fact the migration of a simple SharePoint installation should be pretty straight forward but in the case where there have been customizations been made to the SharePoint applications which is more often than not the case then a customized SharePoint migration solution needs to be implemented

Sophie Moore's profile image

Blog Entry
Migration Options for SharePoint 2013: Consider Your Options Carefully

Use a Migration Solution If you happen to be in one of those camps where you either have a real messy SharePoint data environment or you want to move from an older version of SharePoint, then using a migration tool may be your best option. Migration tools can allow you to clean your content as you move it over

Steven Pogrebivsky's profile image

Blog Entry
Migrating to SharePoint 2010? Know what you’re dealing with first!

I particularly loved asking the two questions during the thrilling and meteoric rise of SharePoint 2007, mostly because no one really had a clue and that allowed me to ask another question, “So do you think you’re aware of all the sites and all the content you have in SharePoint within your organization?

Dave Martin's profile image

Blog Entry
SharePoint 2010 Web Standards, Accessibility, and Usability Quick Reference Guide

” SharePoint Validation Problem Areas – Best Practices Legacy markups & customizations can become a major issues in SharePoint 2007 to SharePoint 2010 Branding Migration efforts Silverlight Web Part(s) and where Microsoft is headed technologically (phasing Silverlight out) WebPartZone specific to SharePoint 2010 WebPartPage specific to SharePoint 2010 ImageField specific to SharePoint 2010 Rich Text Editor specific to SharePoint 2010 Silverlight Plugin Generator Problem SLPG doesn’t escape JavaScript code SLPG uses iframe to solve caching issue with Safari Solution Add comments before loading the JavaScript <script type="text/javascript"> //<!

Errin O'Connor's profile image

Blog Entry
SPC14 Results: 3 Reasons the SharePoint On-Premise roadmap has changed to a severe O365 warning

Using other information as a guide, this means that just like O365 will not be renamed as features are added, a proposed SharePoint 2015 major release will be the last new 'name' and full development cycle that we have been used to since the release of 2007

Adam Levithan's profile image