Carlos Mendible

For those of you who have been trying to automate anything related to Microsoft Teams, let me tell you that there is a new PowerShell Module in town: Microsoft Teams 0.9.0 which you can install with the following command: Install-Module MicrosoftTeams Now to automate the channel creation In A Team you can simply:

In this post I’ll show you how to Use PowerShell to enable Azure Storage Account Firewall Rules. Be sure to be have AzureRM PowerShell 4.4.1 module installed. Login to your Azure Account # Launch Powershell and start by Login to your Azure Account.

In this post I’ll show you how to Use PowerShell to Enable and Automate Azure Analysis Backup. Enable Azure Analysis Service Backup # Enable-AzureRmAnalysisServicesBackup is a small powershell script that uses the the Set-AzureRmResource cmdlet to enable backup location to an Azure Analysis Service instance.

Last week I had the luck to attend the Microsoft Azure OpenHack in Amsterdam. We spent two and a half days learning a lot about kubernetes, Azure Container Services, Azure Container Registry, Azure OMS and Minecraft! In one of the challenges we decided to implement a sidecar container for logging purposes. So using .NET Core we created a console application with proper handling of the"Control+C" and"Control+Break" key shortcuts.

Last week, firewall support was added to Azure Analysis Service (https://azure.microsoft.com/en-us/blog/azure-analysis-services-adds-firewall-support/). The thing is that, at the time of writing, there is no AzureRM cmdlet available to Use PowerShell to Enable Azure Analysis Services Firewall So, with the help of Resource Explorer I found which properties must be added to the service (resource) in order to enable the firewall:

This is a small .NET Core CLI and MSBUILD Cheat Sheet with the list of commands and settings I use almost on daily basis when working with .NET Core, the command line and Visual Studio Code. Checks # Check installed CLI version: # dotnet --version Show available templates: # dotnet new Solutions # Create a solution with the name of current the folder: # dotnet new sln Create a solution with a specific name: # dotnet new sln --name [solution name] Add a project to a solution: # dotnet add sln [relative path to csproj file] Packages # Add package reference to the project in the current folder: # dotnet add package [package name] Remove a package reference from the project in the current folder: # dotnet remove package [package name] Add a specific package version reference to the project in the current folder: # dotnet add package [package name]-v [version] Restore packages: # dotnet restore Create a nuget package for the project in current folder: # dotnet pack Project Templates # Install a new project template: # dotnet new --install [dotnet template name] Remove a project template: # dotnet new --uninstall [dotnet template name] Run test defined in current folder project # dotnet test Builds # Build current’s folder solution or project # dotnet build Build current’s folder solution or project with release configuration # dotnet build -c Release Publish artifacts for current’s folder solution or project. # dotnet publish MSBUILD # To add a reference to a local assembly without nuget package, edit your csproj and add a Reference as shown in the following sample: # <code> <ItemGroup> <Reference Include="[Relative path to the Assembly dll file]" /> </ItemGroup> </code> Force a file to be copied to the output folder, edit your csproj and add a Content section as shown in the following sample: # <code> <ItemGroup> <Content Include="[name of the file]"> <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory> </Content> </ItemGroup> </code> Hope it helps!