I will not make negative comments in my blog. Here is the command to uninstall the Microsoft News widget on Windows 11:
Jan David Narkiewicz (Developer)
Thursday, August 1, 2024
Windows 11: Remove Microsoft News Widget
Sunday, July 28, 2024
Git: get remote URL of local Git Repo
From a console window where the current folder corresponds to a local git repo, run the following from a console:
An example output from this command is as follows:
Wednesday, April 10, 2024
PowerShell: Folder Diff
Wednesday, April 3, 2024
Visual Studio Code: Error Generation Bicep Template from Existing Azure Resource
The latest version of Microsoft's Bicep Extension (v0.26.54) for Visual Studio Code has a new behavior that causes an error message to be generated under certain circumstances. The Bicep Extension was covered in a blog post eighteen months ago (November 26, 2022: Azure: Generate a Bicep Template from an Existing Azure Resource using Visual Studio Code) and the manifesting of the following error message is a newish behavior in the extension:
Tuesday, April 2, 2024
Visual Studio Code: Azure Extension Pack error "Expected value to be neither null nor undefined"
This post presents a solution to the following error displayed in Visual Studio Code when using the Azure Tools Extension Pack:
Internal error: Expected value to be neither null nor undefined: resourceGroup for grouping item
The Azure Tools Extension Pack (Azure Tools) is critical to Azure developers who use Visual Studio Code (see the A below):
When signed in to a subscription, the Azure Tools Extension displays Azure resources by default, grouped by resource group. For some subscriptions (not all) the following error is displayed by Visual Studio Code when group by is set to "Group by Resource Group":
The fix to this issue is to click on the group by icon:
This displays the following context menu:
Sunday, March 24, 2024
Azure DevOps: Requiring Pull Requests to be Associated with a Work Item
Whether following Git Flow, GitHub Flow, GitLab Flow or Trunk-based Development certain policies are standard to source code best practices. For example. each Pull Request (PR) must be associated with a single task/story/epic (a linked work item). This post discusses Azure DevOps support for this feature.
For a given ADO Git repo, branch policies (such a requiring a PR to be linked to a work item) are set per-branch. There is no way to assign such policies to multiple branches. In order to set a branch's policies, navigate to a Repo's branches tab:
For a branch whose policy is to be set, click on the three dots to show the context menu shown below:
Git Branch Strategies
Git Branch Strategy: Git Flow
- Main/Master
- Develop
- Feature
- Release
- Hotfix
Git Branch Strategy: GitHub Flow
- Main/Master
- Feature
Git Branch Strategy: GitLab Flow
- Main/Master
- Feature
- Pre-Production
- Production
Git Branch Strategy: Trunk-based Development
- Main/Master
- Trunk
- Feature
Friday, March 22, 2024
Azure/PowerShell: Geolocating Storage Account White Listed IP Addresses
On a project, we had provided access to to an Azure Storage account by adding permitted IP addresses to the firewall (white listed IPs). These settings can be found via https://portal.azure.com/ by navigating to the storage account and selecting Network under "Security + networking":
I was tasked with writing a script to list all the white listed IP addresses and display there geographic location. The http://ip-api.com returns (for free) the geo data associated with an IP address. This service is free for no-commercial use:
The PowerShell script to return this information takes two required parameters:
- $resourceGroupName: resource group name associated with storage account
- $storageAccountName: storage account name whose white listed IPs will be returned
The script in its entirety is as follows: