So i tried a HoloLens today


Today i participated in the HoloLens Academy and it was an awesome experience.

The actual devices was guarded in a no-personal-electronics-zone so the picture above was the closest my camera came to a HoloLens.

The academy was a walk through with Unity and Visual Studio to create our own HoloLens App.

The first hologram we got to play with was a test app. A remote controlled car that we could get to drive around – Mind Blown ! This actually works !!

But this was a developer session, and we wanted our own holograms. So introducing Unity (beta):

We started by creating a simple scene in Unity, adding a few object. Then we replaced the standard camera with a HoloLens camera and pressed build. After that we needed to open the outputted solution with Visual Studio 2015 and pressed run…

And we got our own holograms, mind blown again 🙂

Then followed a series of making this demo app more and more complex. Adding voice commands, adding object interaction, adding surround sound..

The final state of our app included a hole in the floor where we could look into a “underworld” with bird, clouds and a landscape..

Mind blown again !

Final comments:

If you are using glasses, you need to remove the nose piece, otherwise the “screen” will not be placed correctly.

The field of view is much smaller than the keynote presentation showed us. This does not take anything away from HoloLens, and you forget it after a short while.

This is a awesome piece of hardware, and I can’t wait to try this again, thanks to Dave for being a great mentor during the academy.

Dynamics at //Build 2015

EH-LUMIA2520 - WIN_20150429_095236Right now the keynote for //Build 2015 is running. And something has changed, Dynamics has already being mentioned TWICE !!
At Build 2012 in Seattle Dynamics wasn’t even on a slide with ERP system shown at the keynote.

One more, Dynamics AX mentioned during the Office Graph talk.

Dynamics apps in the new Windows Store For Business

I will keep updating this post with Build+Dynamics impressions.

Stupid error on a friday :)

Today I upgraded a virtual machine running NAV2015 from Update 5 to Update 6. Not a big deal, but during the process I managed to delete the CustomSettings.config file – Stupid mistake on my part.

This file holds the entire configuration for the NAV Service Tier, from authentication of client to SQL Server connection and more.

But the real question I’m left with is:

Why does NAV keep its setting files under C:\Program Files ?

With the introduction of Longhorn (Windows Vista/Windows Server 2008) and UAC – Writing inside c:\Program Files became a elevated operation, so only users with Administrator rights could write there. After that, most programs began to use c:\ProgramData or storing setup and data under c:\Users. There is even a blog from Microsoft on the subject.

Funny enough, SQL Server still defaults its location for DATA under c:\Program files unless changed during the install. They properly keept it there for historic reasons – It has been that way since SQL Server 6.5.

But NAV does not have that history restriction, so from my perspective, this can be added to Luc’s  Lets clean up NAV list.

Anyway, that was my friday rant 🙂