Dave Wolf - SharePoint Champ

Collaboration, Search, Internal Communications Built on SharePoint and Office 365

Page 2 of 5

SharePoint 2016: Six Deprecated Features You Need to Know About

Liam Cleary shares some significant changes we need to be aware of when planning migrations to SharePoint 2016:


Click here for SharePoint 2016 Preview download!

Office 365 ‘App Model’ rename cheat sheet – old booze in new flasks

Check out Jeremy Thake’s cheat sheet with new names for the confusing SharePoint and Office “apps.”

Jeremy Thake

Sophisticated solutions developed by ISVs are in a different league than a hobby project app available from the Office Store.

No question, this created problems justifying a few hundred grand for a year-long effort when the CIO sees the plethora of  ‘free’ and low-cost apps in the Office Store.

Read Jeremy’s full post for more insight and community comments.


Here’s the cheat sheet if you’re in a rush:

Apps for SharePoint (old) SharePoint Add-ins (new)
App Web Add-in Web
App Part Add-in Part
SharePoint App Model SharePoint Add-in Model
Apps for Office Office Add-ins
Office App Model Office Add-in Model


Ignite Conference Breakouts on Channel 9


If you overbooked and missed a session, or that guy behind you with the post-nasal drip drowned out the speaker, here’s your chance to catch up!


PLUS! Vlad Catrinescu  published a script to download and neatly organize the videos and PowerPoint decks from the conference. Thanks, Vlad.


Developing for Keeps? Avoid Stand-alone Deployment!


Are you developing for SharePoint in a commercial organization? Eager to get coding before a well-thought-out development environment is planned and stood up?

Cool your jets! Avoid the temptation to get started early and begin creating solutions in a Stand-alone SharePoint installation!

Standalone deployment option

DO NOT develop in a Stand-alone SharePoint environment if you’re doing serious work!


Wait for your project team to formalize the environmental architecture and provision real farms in which you will do development, even if a farm consists of a single SharePoint server and separate SQL instance.

I have delivered the bad news to a development team up against a tight deadline that their performance problems and some system errors are the result of the Stand-alone deployment.

For starters, if you have Visual Studio, SharePoint (with a boatload of Services enabled), SQL Express, troubleshooting tools, and the Kitchen Sink running in what is likely a 2-core, 4 GB virtual instance on an over-subscribed virtual host, you are already asking for Big Trouble.

Don't paint yourself into a corner with a Stand-alone deployment

Don’t paint yourself into a corner with a Stand-alone deployment!

Most likely you are unaware (as was I until I researched a bunch of errors) that a Stand-alone deployment will not support all ‘normal’ SharePoint functionality. If you look at the Services status page, you won’t see a clue that anything is amiss!

See these caveats from the authoritative TechNet article on single-server SharePoint 2013 installations:

Consider the following restrictions of this method of installation:


Free Stuff!

Don’t you love free stuff?

Some folks like to create and share, like Ayaz Malik. In his site Designzzz, Ayaz provides downloadable resources, links to downloads by others, and how-to advice on all things UI.

The downloads are useful for general web work and SharePoint – especially SharePoint 2013 (and SharePoint Online) with the more open design protocol.

Fonts, graphics (many in native PSD format), style sheets are generously provided with little or no strings. And I’m cautious about strings!

Plenty of ads, but all well-behaved (no annoying pop-ups) when I’ve visited his site.

Check it out – be sure to drop a note of thanks if you use any of the resources. Let me know if you found this helpful.

Good job, Ayaz.

« Older posts Newer posts »