Ready Player One: Bringing a 1990s 2D game to the HoloLens – Nibbles remastered

Now I’m not a HoloLens team member – but recently I’ve been using the device to develop and test an old 1990s classic game “Nibbles” in 2D. A while ago, I wrote remastered the QBasic sample game “Nibbles”, known to many by the name of snake.  This is not a full rewrite, but it utilises some of our…

0

Annotating PDFs with Windows 10

Edge browser on Windows 10 supports web notes, which is a great way to take notes and/or highlight webpages for your own reference or for sharing with others.  Whilst this works great with html content it does not support PDF files, if you try and use this feature with a PDF open in Edge – you’ll…

0

Visualising telemetry in your bot with Application Insights Analytics and PowerBI

In a previous post I showed you how you can add telemetry to your bot.  The sample code linked on my blog allows you to send key/value pairs from anywhere within your bot API to Application Insights.  Also, I showed how you view the tracked data in Application Insights Analytics.  What I didn’t show however, is…

0

Building a FAQ Bot with the QnA Maker Cognitive Service

The QnA Maker cognitive service has fast become the backbone for many customer service bot scenarios.  Once you have created your QnA service and published it, it’s time to incorporate it into your bot framework bot.  To date, there are a couple of ways to implement it from C#. # Option 1 – use the Microsoft.Bot.Builder.CognitiveServices nuget package https://www.nuget.org/packages/Microsoft.Bot.Builder.CognitiveServices You’ll then…

2

DevOps with bots: CI/CD Pipeline with the Bot Framework and Azure – end-to-end walkthrough

So you’re building a bot (C#) and want to involve your stakeholders early in the development lifecycle – no problem, read the steps here and you’ll be able to setup your own Continuous Integration and Continuous Deployment pipeline right into production.  Building bots with the MS BotFramework is no different to building a Web API, therefore we…

0

HoloLens: Inception – The real world within mixed reality

Disclaimer: I’m not on the HoloLens team This week the HoloLens team announced SpectatorView which addresses three key scenarios, including allowing an audience to view what the HoloLens wearer sees on a 2D screen.  This offers a professional grade solution to video capture the holographic content and video stream it in real-time to an external screen.  Essentially the…

0

Botcamp: Building smart bots with Capita using the Microsoft Bot Framework

On 30th January 2017 at Microsoft HQ in Reading, in collaboration with Capita, Microsoft ran a “Botcamp” – an intense activity for a selection of 15 developers from across different Capita Software Services businesses.  The goal was to educate the delegates on the art of the possible with chatbots, by taking them out from their…

0

Windows Store: Declared package dependency does not exist. Dependency: Microsoft.NET.Native.Framework.1.5

Had this yesterday which caused me an issue updating a Windows Store application: “The declared package dependency does not exist.  Dependency: Microsoft.NET.Native.Framework.1.5. Minimum version: 1.5.24614.0.  Please upload the .appxupload file generated by Visual Studio for the Store.” I had already enabled compiling with .NET Native tool chain for the different platforms and was uploading the file…

1

Azure multi-tenant documentation

We have many conversations around developing multi-tenant applications on Azure.  There are some great resources available on this subject, but they are scattered across various sources – so I’ve collated some of them here.   Whilst some of these articles are a little older, many of the concepts still stand true. I’ll update this periodically, so check…

0

Windows Store: Error updating package – Invalid package family name

If you see this error when trying to update an existing application in the Windows Store, chances are that your appmanfest is incorrect. Invalid package family name: {yourpackagename}(expected: {yourpackagename}) Invalid package publisher name: CN={yourpublishername} (expected: CN={yourpublishername}) What you need to do is get the correct cert details to use within the package.appmanifest.  Thankfully, Visual Studio can…

0