My alternative to Pebble

About a year ago I backed the latest kickstarter project from Pebble. The battery life, the timeline and the support for my running app justified the purchase. But as we all know the device never made it to my wrist.

With some money to spare and my birthday coming up I decided to go for the Garmin Forerunner 235. It was favoured over the Apple Watch (yes I’m an Apple fan) because of the battery life and the fact that it is a running watch first and smart watch second. Both have build-in GPS but only the Garmin shows the status.

Garmin FR235

The smart features of the watch are limited to displaying the weather and your appointments, music control including volume and showing notifications. Everything is synced from the (i)Phone to the watch. No reply to messages or snooze of alerts. Pretty limited for a smart watch, but it works for me.

Looking at a message on my watch made me think of the pebble notifications I saw on youtube review, minus the animations. The screen looks like the same e-paper technology is used.

** But wait there is more **

Garmin has it’s own app platform called Connect IQ. There are over 1000 apps in the store you can download and install. The SDK is free and everybody is encouraged to develop something great.

In the end I’m very happy with my watch. Still sad Pebble is no more.

In-dept FR235 review by Dc Rainmaker

Posted in Uncategorized | Leave a comment

Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server

We use SSIS packages to import files. These SSIS packages are run with sqljobs. During deployment the sqljobs are created with a script. That is the plan.

While running the script to create the sqljobs we got an error:

Error 14274: Cannot add, update, or delete a job (or its steps or schedules) that originated from an MSX server

Image courtesy of jesadaphorn / FreeDigitalPhotos.net
Image courtesy of jesadaphorn / FreeDigitalPhotos.net

Most solutions found on the internet talk about the name of the server. When you’ve renamed your Sql Server (yeah right) then you need to update the originating_server column in the sysjobs. This was not the case for us.

Over at msdn someone suggested to look at the variables. The first create sqljob would set the @jobid variable and the second create statement would use that value as input, where it is intended as output. The suggested SET @jobid = NULL before each call to sp_add_job did the trick.

Posted in Development | Tagged , , , | 4 Comments

SDN event March 2017

The SDN – Software Development Network – is a special interest group for dutch developers. Four times a year they organise an event where people present and talk about their passion.

As a member of the SDN you are aware of the latest developments. You are part of a network of professional developers who assist each other in word and deed. This means there is a technical helpdesk at your fingertips so you can book considerable time savings in solving problems.
sdn.nl with Google translate

Here are the talks I attended.

Customer identities in an Enterprise scenario

With slides and demo’s Jurgen showed us the Azure Active Directory Business 2 Consumer (AD B2C) solution from Microsoft. It differs from AD that you don’t know how many users you need in advanced and thus the costs are mainly based on the number of authentications, where AD charges for the amount of users.

The features include self-service (password reset, signup, …), usage of (social) identity providers and extensive login page customisation.

B2C-LoginPage
* Image from blogs.msdn.microsoft.com

Zero-downtime applications with containers

Docker is used for highly available solutions. In the demo a docker swarm was used to host a .net core application. With a visualizer container the setup (1 master and 2 slaves) was visualised on a website.

Using blue-green / rollout scenario’s the upgrade can be performed. Tips for database scheme: support version n-1 and do an upgrade after the last n-1 version of your application is replaced.

Fun fact: presentation had to be done with webcam from laptop #1 pointed to screen of laptop #2 because the projector couldn’t handle the resolution of laptop #2. 😎
docker_picture_in_picture
slides

Progressive web apps and the future of the web

Progressive web apps (PWA) are defined as Reliable (offline), Fast (install/usage) and Engaging (capabilities). It uses a Service worker, which is installed from the website. The Service Worker reacts to events, retrieves data from the internet when online or from the cache when offline.
Interesting links for PWA:

The presentation was recorded and is available on youtube:

Conclusion

A lot is happening and a single developer can’t keep up with all new things. This SDN event is (again) a great way to see what’s happening and get first hand information from experts.

Posted in Conference | Tagged , , , , , , , , | Leave a comment

Renew certificate 2017 edition

Today I used my trusty post Resolve certificate error for Synology Diskstation part 3 of 4 again to renew my certificate. The site startssl.com is still alive, is still free and still works. They even send me a reminder 2 weeks in advanced of the certificate expiring.

Uploading the certificate caused my browser to throw errors. The certificate was not trusted. Not happy 😦

There was some turbulence since last autumn. I totally mist this.

I need another (free) SSL source.

After some searching I ended up using sslforfree.com since I could verify my domain by adding a TXT-record. Other sites needed me to host files or open ftp to them with username and password 😯

To verify my domain using a TXT-record I noticed the google support page was not providing the right solution. The DNS entry should have _acme_challenge for the Host name:

Type Host Value TTL
TXT-Record _acme_challenge R4nD0m57R1n9 1 min

The provided certificate is valid for 90 days. Safari trusts this CA and the certificate. I’m happy again. 🙂

Posted in Security, Tooling | Tagged , | 2 Comments

Workaround for excluding assemblies from code coverage in TFS2015 build

Our build server is TFS2015 and Microsoft promises that we can customize code coverage analysis. But with runsettings setup to exclude assemblies from code coverage exceptions fail the build. Not nice.

Today we figured out how to work around this and exclude an assembly from code coverage. The key was in the msdn article; the pdb file was needed to get code coverage. Would this mean that when the pdb file was not there no code coverage was registered?

The assembly we wanted to exclude was Common.Logging. The nuget includes the pdb file for debugging purposes. We’re about to delete it in our build sequence:

delete_files

exclude_assemblies_from_code_coverage

The delete files step removes the Common.Logging.pdb before the Visual Studio Test step. Now the code coverage is not calculated for Common.Logging. Mission accomplished.

Posted in Development | Tagged , , , | Leave a comment