Feature Framework was (and to some extent, still is) the good old way of provisioning stuff to SharePoint.
This post describes a few different ways of fixing the “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.” error. One can encounter this issue when trying to package/publish a SharePoint solution, web site, or an Azure Webjob. Symptoms Visual Studio throws the following error when packaging a SharePoint solution to a .wsp file when deploying or publishing your web project (for example…Continue reading Fixing the error: “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.”
This post is about fixing one of the most annoyingly unspecific errors that you can get when activating (Feature Framework) features on SharePoint – “File not found”. Whatever that might mean, right? Problem Ugh. A plain and simple “File not found” is one of the more annoying errors one can stumble upon when trying to activate a feature. It usually gets thrown at you quite quickly after hitting the activation button on your feature management page – and it’ll look somewhat like the below: There…Continue reading “File not found”error when trying to activate a custom feature on SharePoint