All Posts

All Posts (530)

• 

  Published on

  2016-10-04 9:53 a.m.

  Authors

  koskila

  Tags

  office-365sharepointsharepoint-2013sharepoint-onlinesharepoint-user-profile-service

  Disabling Delve/MySite redirection from SharePoint Site Collections

  In this post, I outline a simple way to stop SharePoint (either on-premises installation or SharePoint Online) from redirecting to Delve or MySites (respectively). The normal behavior is, that this happens when users click any name of a user anywhere in SharePoint. This is often not desired, and sometimes just confusing or impractical. Problem If your customers are like mine, a lot of them hate Delve or MySite, or both. Or maybe they just aren't willing to yet adopt Delve.

  Read more →

• Published on

  2016-09-16 8:05 a.m.

  Authors

  koskila

  Tags

  azurecode-firstefef6sqlvisual-studio

  Applying Entity Framework's Code-First Migrations against a Database in Azure by running Update-Database

  This post describes how to run Entity Framework's code-first migrations against a database located in Windows Azure. This is done by running the Update-Database commandlet with suitable switches, see below. The problem and symptoms Okay, so you're developing your MVC+EF cool web app with a database in Azure, and you're using code-first migrations. Cool!

  Read more →
• 

  Published on

  2016-09-12 3:34 p.m.

  Authors

  koskila

  Tags

  o365sharepoint-2013sharepoint-add-insharepoint-app-partsharepoint-legacysharepoint-online

  Updating files in an App Part (SharePoint Add-in)

  Luckily, SharePoint Add-ins (or App Parts, like they were called earlier) are slowly getting killed and rooted out of all the sites they once were deployed to - and I don't think anyone's going to miss them. However, as so often happens with legacy implementations, there will still be thousands of sites, where SharePoint administrators and developers will be responsible for maintaining and developing the solutions further.

  Read more →
• 

  Published on

  2016-09-02 10:41 a.m.

  Authors

  koskila

  Tags

  powershellsharepoint-online

  Fixing "Connect-SPOService : Identity Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in." -error

  This post describes my super-simple fix to a weird error about "Identity Client Runtime Library (IDCRL)" failing with federated sign-in when running PowerShell scripts against SharePoint Online. One typical form of the error might be something along the lines of " Identity Client Runtime Library (IDCRL) could not look up the realm information for a federated sign-in. " coming up.

  Read more →
• 

  Published on

  2016-08-25 9:53 a.m.

  Authors

  koskila

  Tags

  cef6iisvisual-studiovisual-studio-2015visualstudio2017visualstudio2019

  Exception of type 'System.OutOfMemoryException' was thrown.

  This post describes one of the more no-brainerish ways of fixing a 'System.OutOfMemoryException' exception being thrown in your ASP.Net MVC application using C# and Entity Framework. Problem While developing a web project, for example, an ASP.NET MVC web application that is using EF, sometimes when handling a lot of data or complex entities on your dev machine, you encounter this error: OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.] System.Text.StringBuilder.

  Read more →
• 

  Published on

  2016-08-02 10:15 a.m.

  Authors

  koskila

  Tags

  react-jstypescriptvisual-studio-2015

  Fixed: Cannot use JSX unless the '--jsx' flag is provided

  This blog post is about fixing issues related to building a project with TypeScript files. Basically, if your jsx or tsx -files are not getting built to js-files (which is what the browser understands) in Visual Studio's build, this post might solve the issue for you. Description Whilst converting a project using React.js to TypeScript (and, hence, to use .ts and .tsx files instead of .js and .

  Read more →
• 

  Published on

  2016-07-25 11:50 a.m.

  Authors

  koskila

  Tags

  visual-studiovisual-studio-2010visual-studio-2013visual-studio-2015

  Tip: Scroll Solution Explorer to current file in Visual Studio 2012, 2013, 2015 and 2017

  This quick post describes how to get the Solution Explorer to actually track your currently open file. For some reason, this extremely useful feature is disabled by default in Visual Studio. Enabling it helps you to better conserve your context, and see which part of your solution you're in, while you're developing a complex piece of software. Give it a try, in case you haven't already! It's great and extremely useful! :)

  Read more →
• 

  Published on

  2016-06-07 6:35 a.m.

  Authors

  koskila

  Tags

  asp-netconfigurationcefsql

  Solving the "Spatial types and functions are not available ..." -problem

  This page describes multiple ways to fix the ' Spatial types and functions are not available for this provider because the assembly ‘Microsoft.SqlServer.Types’ version 10 or higher could not be found. ' exception which comes up during debugging or publishing your program, app or service using DbGeography. Symptoms While running a console program or perhaps installing an ASP.

  Read more →
• 

  Published on

  2016-05-29 12:52 p.m.

  Authors

  koskila

  Tags

  code-firstcefef6sql

  Fixing the error: "Column XX in table dbo.YY is of a type that is invalid for use as a key column in an index."

  While using Entity Framework and code-first migrations, Entity Framework (EF) creates the indexes for you - but what if you need to create a custom one, explicitly based on a certain field/column? Then you'll have to tell EF which one to use as a key column.

  Read more →
• 

  Published on

  2016-04-05 12:44 p.m.

  Authors

  koskila

  Tags

  displaytemplateoffice-365powershellsharepoint-onlinesharepoint-searchsharepoint-user-profile-service

  RefinableString -managed property in SharePoint Online not populating for all items

  This post describes a peculiar problem that a customer had. In their intranet, all of their employees had a managed metadata -typed managed property in SharePoint User Profile Service and a mapping from that property to RefinableString31. RefinableString31, in turn, was used on Search DisplayTemplates to show the textual value of the managed metadata field. Symptoms The mapping and displaying of the values worked beautifully - except for one user.

  Read more →
• 

  Published on

  2016-03-17 12:43 p.m.

  Authors

  koskila

  Tags

  managed-metadataoffice-365sharepoint-2013sharepoint-online

  Tweaking the SharePoint list view search box to filter on managed metadata fields

  This post contains a really small, but nifty tweak to the search box in SharePoint list views. Applies to 2013, and Office 365 (for now). Pretty basic stuff, but had to figure this out for a customer so can just as well document it here :) Okay - so a customer needed to be able to filter view items in a SharePoint list by values in a keyword field (managed metadata, with values added by editor users), and wanted to use SharePoint's search box.

  Read more →
• 

  Published on

  2016-02-14 9:02 a.m.

  Authors

  koskila

  Tags

  asp-netcdisplaytemplatemvcmvc5

  Duplicate object values in ASP.NET MVC Display Templates? Easy fix!

  Are you getting duplicate object values (or whatever those Objects output in .ToString())? Eh, so was I, after I edited the display template for String. Found a fix, though. Description Okay - I just ran into one of my more stupid mistakes since.. Well, since forever. I had made some quick and simple edits in String.cshtml display template (among quite a few other edits before building again and seeing what happened), as I added support for Enum values there.

  Read more →
• 

  Published on

  2016-02-07 9:36 a.m.

  Authors

  koskila

  Tags

  asp-netazurecode-firstcefef6mvcmvc5

  Fixing "An error occurred while updating the entries" while running code-first migrations in MVC 5 app

  This post describes an issue with EF's code-first migrations, when mapping between DB's DateTime (datetime2) and C#'s DateTime simply fails, and results in the Update-Database cmdlet failing, too. It is more or less a prime example of a situation, where the error itself tells very little about the actual issue, and since debugging code-first migrations is kind of difficult ( see the best tips for that here! ), it's cumbersome to investigate.

  Read more →
• 

  Published on

  2016-01-29 9:52 p.m.

  Authors

  koskila

  Tags

  azurenetworksqlvisual-studio

  Fixing error "Cannot open server - - requested by the login. Client with IP address - - is not allowed to access the server." in Azure deployments from Visual Studio

  This article explains how to work your way around the exception 'Cannot open server - requested by login...' The issue is caused by Azure's firewall logic, which might sometimes appear a little bit overzealous for simple development workloads, and might stop you from accessing your databases from your development machine. But just as everything else in Azure, the firewall exists for a reason, and working with it just requires a couple of extra clicks, is all.

  Read more →
• 

  Published on

  2016-01-21 1:37 p.m.

  Authors

  koskila

  Tags

  on-premisespowershellsharepoint-2010sharepoint-2013sharepoint2016sharepoint2019uls

  Using PowerShell to set ULS logging level to "extra verbose" to catch all the events in the logs

  This blog post describes how to set SharePoint's ULS level to "Extra Verbose" (VerboseEx) using PowerShell. This is not possible using the browser UI, so some POSH magic is required! Luckily, it's quite straightforward, but to avoid filling your hard drive(s) with huge log files, you should reset the level when you're done debugging! Description of the solution By default, ULS logging is somewhat non-detailed. This means that a lot of data that could be used to debug issues is omitted.

  Read more →
• 

  Published on

  2016-01-05 12:02 p.m.

  Authors

  koskila

  Tags

  powershellsharepoint-2010sharepoint-2013sharepoint2016spweb

  Using PowerShell to modify anonymous access permissions on SharePoint On-Premises

  This post is about managing Anonymous Access on a SharePoint site (SPWeb) using PowerShell commandlets. It's often a lot more feasible and even easier than using the browser interface! In some cases, it's borderline impossible to avoid it anyway - since accessing the GUI switch might not be possible. Description Assume you have a site collection that you have published to the whole world.

  Read more →
• 

  Published on

  2015-11-17 9:12 a.m.

  Authors

  koskila

  Tags

  deploymentfull-truston-premisessharepoint-2010sharepoint-2013wsp

  Powershell Error: Cannot uninstall the LanguagePack 0 because it is not deployed.

  Have you ever run into this, very non-descriptive and weird SharePoint error message "Cannot uninstall the LanguagePack 0 because it is not deployed"? You could encounter it while running some PowerShell scripts - most typically when trying to update a wsp solution. I have, and luckily often easily solved! Symptoms Assume you're trying to install, update or uninstall a SharePoint solution (.

  Read more →
• 

  Published on

  2015-10-20 1:23 p.m.

  Authors

  koskila

  Tags

  asp-netdeploymentfull-trustiissharepoint-2010sharepoint-2013sharepoint2016

  "Server Error in '/' Application" or "Parser Error" - it's actually a malformed web.config killing your ASP.NET-application or SharePoint

  This post describes how to resolve a kind of cryptic and oddly misdescriptive error message about Parser Error on your ASP.NET application or (an On-Premises) SharePoint site. I ran into this after deploying wsp-packages to a SharePoint farm, but you can apparently get this on ASP.NET MVC sites, too. The error doesn't actually tell you what's wrong, so figuring it out took a while. Though hopefully, it helps you!

  Read more →
• 

  Published on

  2015-10-01 7:16 a.m.

  Authors

  koskila

  Tags

  sharepoint-2010visual-studiovisual-studio-2010

  Visual Studio 2010 fails to show the design view of an aspx-page

  This post is about solving the issue with Visual Studio 2010 failing to show the design view of an .aspx-page. Luckily, it's an easy and pretty classical fix. Symptoms Whilst trying to view or edit an aspx-page in design mode within Visual Studio 2010, the window is just plain empty and there's little you can do about it - selecting view markup or hitting F7 may not do anything, and restarting the Visual Studio doesn't help.

  Read more →
• 

  Published on

  2015-09-21 1:38 p.m.

  Authors

  koskila

  Tags

  full-truston-premisessharepoint-2010sharepoint-2013sharepoint2016wsp

  The quickest way to download all the wsp-packages in a SharePoint farm

  Sometimes - pretty often in the good old on-premises world, actually - you'll need to have a copy of all the packages that are deployed to a certain farm. So - how to download all of the deployed farm solutions (essentially, cabinet files renamed to .wsp) from a farm? Luckily, it's quite easy! Solution To download all deployed farm solutions (wsp-packages) from a SharePoint farm is pretty simple using PowerShell. No need to download individual packages through cumbersome interfaces!

  Read more →
• 

  Published on

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

  Authors

  koskila

  Tags

  azuredeploymentfeature-frameworkfull-trustmsbuildsharepointsharepoint-2010visual-studiovisual-studio-2010visual-studio-2013visual-studio-2015visualstudio2017visualstudio2019webjob

  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

  office-365sharepointsharepoint-2013sharepoint2016sharepoint2019sharepoint-online

  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

  internet-exploreroffice-365sharepoint-2010sharepoint-2013

  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

  cfull-trustsharepoint-2010sharepoint-2013threading

  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

  cfull-trustsharepoint-2010sharepoint-2013sharepoint2016spweb

  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 →