I wanted to authenticate my SignalR connections using my OWIN application cookie. I couldn’t find any way to do this so here is the attribute I had to make. Is this necessary? If not, please let me know… Continue reading Authorize attribute for SignalR using OWIN Application Cookies
If you get this error when running Umbraco on Azure, you need to set the web app to run in 64 bit.
Cors is your best friend and worse enemy. Continue reading Part 2 of annoying app dev gotchas – Making api requests
Man that is a lot of buzzwords. Here be dragons. Continue reading Use Azure Mobile App Authentication to login using Facebook with a .NET Backend for Cordova with Ripple
I like the new Code column in Visual Studio 2015’s Error List, but I don’t like using Bing.
Continue reading Change the default error search in Visual Studio 2015 from Bing to Google
Enable-O365integration : Credential cannot be authenticated
At line:1 char:1
+ Enable-O365integration -o365accountupn "xxxxxxxxxxxxxxxxxxxxxxxxxxx" -Pas ...
+ CategoryInfo : InvalidOperation: (:) [Enable-O365Integration], O365ConfigureException
+ FullyQualifiedErrorId : InvalidInvoke,Microsoft.WindowsServerSolutions.O365Integration.EnableO365IntegrationPSCmdlet
If you ever get this error you need to disable the windows azure active directory sync in the Dashboard before continuing
If you are ever using a LinqDataSource and want to join a second table, bad news, you can’t. BUT if your edmx file sees the join between the tables, you can still reference it.
See following extract from the ASP.NET file:
<asp:LinqDataSource ID="LinqDataSource1" runat="server"
Select="new (ID, Name, Author.Name AS Author)"
This Kaseya error can be quite annoying to diagnose if you don’t know what to look for.
It is caused by having a step (such as Set Registry Value) with < or > in it, as Kaseya use XML to save their scripts.
You can double tag it, eg <<br>> instead of <br> and it will run as expected.