If you are using OpenSSH on Windows the default shell used when connecting is cmd.exe. To update Windows to use something different you need to update the registry and restart the OpenSSH service.

Taken from https://andrewchaa.netlify.app/posts/2020-05-27/service-fabric-skeleton-service/ to conserve and update as needed as could not find it when I went looking for it.

On Service fabric, you can either create ASP.NET Core API service or worker process. I’m going to create a worker service today

So, you made some commits and then realise you used the wrong author and email address. No problem, use the following command to update them all and then you can push with consistent happiness.

Because I am lazy I wrote a script so I can update all my machines from the one location which is the gist below. This works in powershell core. Again this is mostly for me but feel free to use as needed.

This is a update to Using git aliases. A few extra commands and a bit of a cleanup. I should move it to a gist at some point.

Update: Moved the contents to a gist.

This is more for me than anyone else. If you want to move to PowerShell core in Visual Studio Code then do the following.

1. Press CTRL + , to open settings.
2. Enter Shell: Windows in the search box.
3. Scroll down to Terminal > Integrated > Shell: Windows
4. Click on ‘Edit in settings.json’ and add the following.

I work with git for home and work project, I recently found you can use alias across all platforms due to the way it runs on windows. So all these aliases will work happily on git for windows and hopefully will make you work day more streamlined.

Some are from sites I have found and other I have created myself.

The site seems to be down. This was handy for something I was playing with.

Case Converter was made when I wanted the text to display in a WPF UI in upper case. Probably not the best class name, but anyway. To get the code and install read on. Make any UI string uppercase. Once you have registered the resource and created the class just use the converter in the element you want converted.

Procmon is created by sysinternals and should be deployed to any server in your enterprise (and desktop) it allows you to see what file, registry, network and processed & thread activity is happening on your system. I just used to to work out why VS 2010 was not installing, it turns out it iterates through all the drives on your system including your mapped drives. As I had just been playing with WebDav I had a mapped WebDav drive which was very slow to access. Looking at proc mon I could see straight away what the issue was and I disconnected the drive. Problem sovled!

Procmon is created by sysinternals and should be deployed to any server in your enterprise (and desktop) it allows you to see what file, registry, network and processed & thread activity is happening on your system. I just used to to work out why VS 2010 was not installing, it turns out it iterates through all the drives on your system including your mapped drives. As I had just been playing with WebDav I had a mapped WebDav drive which was very slow to access. Looking at proc mon I could see straight away what the issue was and I disconnected the drive. Problem sovled!

You may find this code block handy: [csharp] /// /// Gets the mail item selected in the explorer view if one is selected or instance if that is the view active. /// /// The instance containing the event data. /// A Outlook.MailItem for the mail being viewed. private Outlook.MailItem GetMailItem(RibbonControlEventArgs e) { // Check to see if a item is select in explorer or we are in inspector. if (e.Control.Context is Outlook.Inspector) { Outlook.Inspector inspector = (Outlook.Inspector)e.Control.Context; if (inspector.CurrentItem is Outlook.MailItem) { return inspector.CurrentItem as Outlook.MailItem; } } if (e.Control.Context is Outlook.Explorer) { Outlook.Explorer explorer = (Outlook.Explorer)e.Control.Context; Outlook.Selection selectedItems = explorer.Selection; if (selectedItems.Count != 1) { return null; } if (selectedItems[1] is Outlook.MailItem) { return selectedItems[1] as Outlook.MailItem; } } return null; } [/csharp]

Just read this article, it is a great example of how the memory dumps can be used to trace issues and also points out a workaround to solve this problem prior to a patch being released. http://www.todd-carter.com/post/2010/02/08/SharePointe28099s-Sasquatch-Memory-Leak.aspx

If you want to have the Visual Studio command prompt on the right-click on the folder place the below into a text file with a .reg extension and then add it to the registry.