According to Github, with this new feature, developers will be able to configure the repository automatically and with as little effort as possible. It eases the work involved in scanning code in Python, JavaScript, and Ruby repositories.

Code scanning on GitHub is done using the CodeQL engine, and while it supports a wide variety of compilers, the feature is currently only available for Python, JavaScript, and Ruby. GitHub’s Walker Chabot says this will change very soon as the company looks to expand support to additional languages and will aim to have this in place by the summer.

Once “Enable CodeQL” is enabled the feature will automatically start looking for flaws in the repository.

The official GitHub blog also says that code scanning is free for everyone, and that enterprise users can also take advantage of it through the GitHub Advanced Security for GitHub Enterprise service.

Two new features are now available in Intune. The first has to do with configuring feature updates. This allows IT administrators to create policies that control which Windows feature updates are delivered to devices. Devices will remain on the version they have specified in their policy until IT administrators set a newer version of Windows in this section.

Some other useful settings that you can configure are to choose whether the update becomes available immediately, on a specific date, or through a staged rollout. The latter option also allows you to choose when the first and last groups will receive the update, as well as the interval of days between them.

The second option mentioned above is accelerated quality updates. But there are a few settings to watch out for. One lets you choose the minimum OS version that all devices should be on, and the other lets you decide how long a device can delay an update before needing a reboot. But be careful when using the former. It only gives users a 15-minute warning after downloading the update before forcibly installing it via reboot.

Deployment of expedited updates is done without the need to pause or edit your existing monthly servicing policies. For example, you might expedite a specific update to mitigate a security threat when your normal update process wouldn’t deploy the update for some time.

Expedite updates uses available services, like WNS and push notification channels, to deliver the message to devices that there’s an expedited update to install. This process enables devices to start the download and install of an expedited update as soon as possible, without having to wait for the device to check in for updates.

But that’s not all. You can also track delivery reports on feature updates and accelerated quality updates. You can find these in the Reports tab, then select Windows updates in the Microsoft Endpoint Manager Administration Center. They display alerts, device-level granularity information, and overall results.

Azure supports two types of queues: the Azure Storage queues and Azure Service Bus queues.

To work with the code examples, you should have Visual Studio 2019 installed in your system.

Create a console application project in Visual Studio

First off, let’s create a .NET Core console application project in Visual Studio. Assuming Visual Studio 2019 is installed in your system, follow the steps outlined below to create a new .NET Core console application project in Visual Studio.

• Launch the Visual Studio IDE.
• Click on “Create new project.”
• In the “Create new project” window, select “Console App (.NET Core)” from the list of templates displayed.
  Click Next.
• In the “Configure your new project” window shown next, specify the name and location for the new project.
• Click Create.

What is Azure Queue Storage?

Azure Queue Storage is a Microsoft Azure cloud service that enables you to store vast numbers of messages for processing. You can take advantage of authenticated HTTP or HTTPS calls to access messages from anywhere in the globe in a secure manner. The maximum size of a queue message is 64 KB. A queue in Azure Queue Storage can store huge numbers of messages (even millions), up to a maximum storage capacity of 200 TB.

Like your other Azure Storage data objects, including blobs, files, and tables, your queues are stored in your Azure Storage account. The Azure Storage account gives you a distinct namespace for your Azure Storage data, which you can access over HTTP or HTTPS from anywhere on the world.

Install the Azure.Storage.Queues NuGet package

To work with Azure Queue Storage, you should install the Azure.Storage.Queues NuGet package into your project.

You can install this package from the NuGet package manager or by running the following command in the package manager console window.

Create an Azure Queue Storage client

If you don’t already have an Azure Storage account, you should create one using the Azure Portal or Azure PowerShell or Azure CLI. Then copy the connection string and the account access keys because you’ll need them to connect to your Azure Storage account.

Send and receive messages using Azure Queue Storage

The following code snippet illustrates how you can send messages using Azure Queue Storage.

Add a message to a queue in Azure Queue Storage

You can add a message to queue in Azure Queue Storage using the SendMessage method.