Skip to main content

Lost In The Framework

Search This Blog

Cmon, cmon, cmon, cmon now touch me babe!

on February 19, 2017

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Great online touch typing course.

Be careful though, it steals your focus!

Get link
Facebook
Twitter
Pinterest
Email
Other Apps

Comments

Post a Comment

Popular Posts

Creating a Dark Mode for Windows Forms Applications

I recently decided to spruce up one of my Windows Forms applications, to make it more modern and Windows 10-like. The original look and feel was old fashioned: I know what you’re thinking: “Windows Forms? In this day and age? Why not a web app? Why not WPF?” But this is Syncify - a desktop app to re-title MP3 files. And I am way more productive in Windows Forms… As part of the face-lift I decided to create a dark mode. This is what I implemented: Detect whether the user has dark mode selected . On Windows 10 this is a case of checking the registry for the newer Light Mode. If that is not selected, then my app uses its dark mode. private static bool UsingLightTheme () { var registryKey = Registry . CurrentUser . OpenSubKey ( @"Software\Microsoft\Windows\CurrentVersion\Themes\Personalize" ); var appsUseLightTheme = registryKey ?. GetValue ( "AppsUseLightTheme" ); if ( appsUseLightTheme is null ) {

Installing Visual Basic 6.0 on Windows 10 and Windows 11

It has been nearly 25 years since Microsoft last released Visual Basic . The first version came out in 1991, version 6 was released in 1998. And due to its popularity, VB6 applications are still in widespread use. In my company, a VB6 application is the main LOB system used by an entire department. During our latest laptop refresh we decided that my teams will run the company’s locked-down laptop image and will run on standard hardware. This pretty much stops us from doing our day-jobs as we currently run as local administrators on high-spec kit. Instead, we’re going to run high-spec VMs in Azure and I’ve been creating some developer VM images so that my teams can get up and running quickly and don’t have to spend days building their new developer machine. So, this means, for the team supporting the VB6 application, I needed to figure out how to install Visual Basic 6. This took a considerable amount of trial and error and plenty of time Googling. Below are the steps that work

Migrating Jira Sprints to Azure DevOps Iterations

Up to now my teams have always had a heterogeneous approach to Application Lifecycle Management. In other words, we've used a variety of tools: Jira – for tracking work Subversion – for source code TeamCity – for automated builds and continuous integration Octopus Deploy – for "one-click" deployments to dev, test and production environments This year, however, we've finally taken the plunge and started using a single tool for all this: Azure DevOps (ADO). For each of the 4 capabilities we've had to plan and execute migration tasks. For the migration of work from Jira I've been using Solidify's migration tool . It's pretty nifty! It downloads Jira issues into JSON files which are then pushed up into Azure DevOps. As part of the process you specify mappings for issue types, fields and users. One thing it doesn't cover so well is the migration of Sprints. In Jira information on Sprints, particularly past Sprints, is opaque.

Powered by Blogger