Some time ago I was searching a touch display for a project of mine. The requirements were 7 inch in size, capacitive touch digitizer and at least a resolution of 800x480px. I figured out Waveshare’s “7 inch HDMI LCD (B)” would be the perfect match. And I was thrilled that not only it was not only relatively cheap, but they got it right and (so the claim) implemented “fully valid” HID protocol (their shop still states “When work as a computer monitor, supports Windows 10/8.1/8/7, five-points touch, and driver free”).
When I received the display, everything was working out of the box with my Raspberry Pi 2 running on Windows 10 IoT. Then the Anniversary Update came and that’s when things got weird. Over-night my slightly laggy touch display turned into one that responded to scroll movements, but I could hardly get a “click” to trigger. Later I found that thread over at the MSDN support forums: Waveshare 7 inch display doesnt work on windows 10 iot core
After a few days of discussion Microsoft acknowledged that there was some change in the HID report processing pipeline, which now discards HID reports that are malformed. The advice was to contact Waveshare to see what they could do about the issue. Long story short, I never got a satisfying answer. So I decided to fix it on my own.
You might remember I published a Nuget package to help integrate NLog with OWIN back in December 2014. And it worked great so far! A few weeks ago I got a notification from Github that my name was mentioned in some issue. Long story short, the main NLog maintainer and I decided to move Pysco68.Owin.Logging.NLogAdapter over to the NLog organization to give it a bit more visibility.
So there we go; from today on, you should use NLog.Owin.Logging to get OWIN and NLog together. Oh, and there’s a new Nuget package too: NLog.Owin.Logging@Nuget.
The usage remains the same:
Hello folks – just a quick post!
I finally found the time to publish a workaround I wrote back in May this year. I was hacking a fully automatic irrigation system (garden stuff you know ^^) and because I had to do that really quickly (before leaving for vacation) I decided go the route of a known framework: OWIN, ASP.NET WebAPI 2, NOWIN (as a host), Identity 2.0, EntityFramework, MariaDB, a good HTML5 stack… etc…
Well mostly a known framework; I had to run on a Raspberry and Microsoft wasn’t quite as ready with Windows 10 IoT as I’d needed it… So it was a quick decision to stick with Raspbian and Mono. Which by the way work out great. At the time of writing my little application has over 140 days of uptime! – Yay –
I’ll probably write more about the whole project in the next months!
Anyhow I faced the problem that the MySQL Connector/NET is *still* (I posted the bug on November 7th 2014 – Bug Ticket: #74726 EF migrations fail on long foreign keys) having issues with code first migrations, long entity names and foreign keys… and as I really lost any confidence that ****** is going to fix that any-time soon I decided to do it on my own…
Tl;dr: You can use NTLM authentication without relying on IIS or HttpListener in OWIN projects by using my OWIN autentication middleware: more information on my Github project: Pysco68.Owin.Authentication.Ntlm middleware. It’s working flawlessly with ASP.NET Identity 2.0! And there’s a Nuget package too!
As you may have noticed, I’m relatively busy these days with things like OWIN and surrounding technologies. All there shiny and new things that just fit together so well. And then you have customers just requiring plain old things like NTLM for their latest shiny intranet application.
Two Days ago we came back home from our wonderful 3 week trip to Eastern Canada, besides the stunning landscape and the open-hearted people we met, we tasted lot of delicious things (Maple Sirup, Chocolatines, Lobster, Beer from regional breweries and Homemade Raspberry Lemonade).
After an hour of hiking around the confluence of the Saint Lawrence and Saguenay river and 1 hour of watching belugas we were looking for something to eat. Locals recommended us the “Le Café Bohème” (should you ever be in Tadoussac, just go there) where we had a very good pizza with salad and a truly remarkable Homemade Raspberry Lemonade. It was delicious! The sourness from the lemons complemented the taste and the sweetness of the raspberries perfectly.
Back home the heat (a whopping 32°C in the shadow) is hitting us very hard – but we remembered the delicious and refreshing lemonade! Thus we made our own Homemade Raspberry Lemonade. And of course we are sharing our recipe with you.
On a recent machine-to-machine communication scenario I needed to enable secure push messages. The server side of the project was plain ASP.NET Web API 2 (on OWIN – I just love it) so dropping in SignalR and a few hubs was done in minutes. The tricky part was that I was using the Hawk authentication scheme to secure the access (and I was very happy on how it worked out so far). So no reason to change anything about the global setup if it wasn’t for the .NET SignalR client library not supporting Hawk out-of-the-box.
But luckily SignalR sources can be crawled through easily over at github (https://github.com/SignalR/SignalR). And even more luckily I found that it would be no more that a few lines to wire it up with Thinktecture’s Hawk implementation (Thinktecture.IdentityModel.Hawk on Nuget).
So there you go, my latest, greatest Nuget packages is: Pysco68.SignalR.HawkHandler.
BTW. there’s some news about that topic: My NLog OWIN adapter went “official”
While playing around with OWIN, WebAPI 2 and the other new kids I was missing a logger factory for my favorite logging framework: NLog! And I wouldn’t be a good software engineer if I didn’t wire this up in a nice tiny library.
There you go: Pysco68.Owin.Logging.NLogAdapter on GitHub
And to make it a breeze I built a Nuget package for this one! That means that you can now use NLog as logger for your next OWIN project just by doing this:
Voila! If you’d like to customize the log-level translation table just take a look at the Github page!
Note: this is not a logging middleware! If you want some of those Google is your friend. The log factory (it’s an implementation of Microsoft.Owin.Logging.ILoggerFactory in fact) does provide an implementation of ILogger that wraps arround NLog.There’s some pretty good information about the architecture at Tugber Kugurlu’s blog / introduction to OWIN Logging.
I really hope you enjoy this one! Leave a comment if you have any question or suggestions! Contributions are welcome, just fork and create a pull request, I’ll review it for sure!
Yesterday I showed you my last Christmas present. Now it’s time to show you what I made for me to wear at Christmas. It’s a pretty dress which I saw in the November Burda issue. You can find the pattern as a single pattern here (in German) and here (in English). Continue reading
Hello again! Christmas’ approaching with giant steps and I finally have some free time to write again. After sitting on my desk for a short while, here are the remaining steps for the restoration of the Dual CS 606 record player. For those of you who haven’t read the first part: Dual 606 record player – Restoration (part 1).
In this second part we will focus on getting the electronics up and running again. This involves replacing all the capacitors and checking/cleaning the pots, switches and finally checking solder joins.
Finally I finished my last Christmas present! Another Norwegian sweater in blue and off-white for Yannic. There is no problem blogging it before Christmas, because he sat the most time right next to me while I was knitting. Plus he chose the pattern for the sweater and from time to time he had to try it on. With the yarn left over I made a matching bonnet. It will also be a Christmas present but not for him.