All Posts

All Posts (560)

• 

  Published on

  2015-09-03 3:27 p.m.

  Authors

  koskila

  Tags

  AzureDeploymentMSBuildSharePointVisualStudio2017VisualStudio2019WebjobDevEnvironmentFeatureFrameworkFullTrustSharePoint2010VisualStudioVisualStudio2010VisualStudio2013VisualStudio2015

  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 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 .

  Read more →
• 

  Published on

  2015-08-07 2:31 p.m.

  Authors

  koskila

  Tags

  SharePointSharePoint2016SharePoint2019M365SharePoint2013SharePointOnline

  How to log into SharePoint as a different user

  SharePoint Server 2013, 2016, and 2019 versions don't have that old and familiar "sign in as a different user" option in the site menu, and for the time being, nor does SharePoint Online . However, sometimes it's very useful functionality to have, so it's a bit weird Microsoft chose to get rid of the option. This post outlines a method that I've found to work quite well for making SharePoint ask for credentials so that you can use another account to then log in!

  Read more →
• 

  Published on

  2015-07-22 9:33 a.m.

  Authors

  koskila

  Tags

  InternetExplorerM365SharePoint2010SharePoint2013DevEnvironment

  Identifying IE11 compatibility mode in SharePoint

  In this post, I describe how you can figure out if IE11 (Internet Explorer 11) has jumped into compatibility mode. You will run into this requirement every now and then when trying to figure out some SharePoint browser compatibility mess-up. This is quite frequent because in compatibility mode IE does its best to screw up your CSS.

  Read more →
• 

  Published on

  2015-07-02 9:20 a.m.

  Authors

  koskila

  Tags

  CSharpThreadingFullTrustSharePoint2010SharePoint2013

  The simplest way to create a thread on SharePoint

  This post describes the easiest (probably) and most straightforward way of creating a new Thread in your SharePoint (or any other .NET) server-side/desktop code. Solution Let's face it - one should not create new Threads lightly when developing SharePoint solutions, but sometimes it is difficult to avoid. Or sometimes it's just the simplest way to get around weird framework limitations.

  Read more →
• 

  Published on

  2015-06-27 4:47 p.m.

  Authors

  koskila

  Tags

  CSharpSharePoint2016SPWebFullTrustSharePoint2010SharePoint2013

  How to properly use SPWeb.AllowUnsafeUpdates

  At times you may need to allow unsafe updates for SPWeb objects in order to get your code to run. This, in SharePoint's C# full-trust code, is done by setting SPWeb.AllowUnsafeUpdates to true. However, as this is an exception to security settings, you should generally avoid it. When you can't, it is good practice to limit the change to as small a scope as possible. This is true even though the setting only persisted for the duration of the request (unless the SPWeb object was gotten from SPSite.

  Read more →
• 

  Published on

  2015-06-20 9:41 a.m.

  Authors

  koskila

  Tags

  FeatureFrameworkFileNotFoundSharePoint2010SharePoint2013DevEnvironment

  "File not found"error when trying to activate a custom feature on SharePoint

  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.

  Read more →
• 

  Published on

  2015-06-13 8:55 a.m.

  Authors

  koskila

  Tags

  DebuggingIISW3WPWindowsDevEnvironmentVisualStudio

  Attaching the Visual Studio debugger to the right IIS worker process

  Every now and then comes the time when you'd actually need to debug something, and then you'll likely be using your Visual Studio to attach the debugger to one or more processes. Using CKSDev to attach to all IIS worker processes (w3wp.exe), or if you don't use CKSDev, just pressing ctrl+p and selecting the processes from the list, is often a good enough solution. However, sometimes that makes your dev box sluggish, or maybe catches exceptions from code you're not wishing to debug at the time.

  Read more →
• 

  Published on

  2015-06-05 3:25 p.m.

  Authors

  koskila

  Tags

  CSharpSharePoint2016FullTrustOnPremisesSharePoint2010SharePoint2013

  Programmatically creating readable internal names for new SharePoint fields

  This post is about a small programmatic workaround to creating new SPFields for SPLists in SharePoint with human-readable internal names. This is mainly a usability improvement for your editors (and doesn't change your life that much), but they should appreciate it at the very least! In short, I'll show you how to avoid SharePoint's dirty encoding (like replacing a space with "_x0020_"). This applies when you're using server-side code to generate fields.

  Read more →
• 

  Published on

  2015-05-31 8:52 a.m.

  Authors

  koskila

  Tags

  ConfigurationHostsNetworkWindowsDevEnvironment

  Troubleshooting guide for Windows hosts file

  This post describes how to fix possible issues with the Windows hosts file. I'll first document how to find the damn file, and then go through a bunch of options on what to check and how to fix different possible issues. Opening the hosts -file First of all, the host's file location is usually: C:\Windows\System32\drivers\etc\hosts (link may or may not work depending on your security settings and browser version, but you can always copy-paste it to your text editor's "Open"-dialog...

  Read more →
• 

  Published on

  2015-05-28 8:41 a.m.

  Authors

  koskila

  Tags

  AuthenticationIISRegeditDevEnvironmentOnPremisesSharePoint2010SharePoint2013WindowsAuthentication

  Windows Authentication fails on SharePoint for all hostnames (other than localhost)

  This post describes how to fix Windows Authentication on a SharePoint server that is failing on other local addresses other than localhost. Symptoms You get the standard Windows/Basic Authentication prompt when accessing your SharePoint site, but the site won't accept your credentials when you are accessing the site using an address like http://website. However, using an address like http://localhost works fine (but of course may cause other problems).

  Read more →