deadlydog

Things to include in every application / service

Some things that every application or service you build should have:

• Logging (preferably centralized)
• Metrics (to know how the app is performing (slow endpoints, etc.))
• Alerts (to be notified when things aren't working properly)
• Telemetry (to know which parts of the app / service are used most, or not at all and can be removed)
• User Feedback Mechanism (so users can easily report issues or request new features)
• Feature Flags (to enable rolling features / changes out in a controlled manner)

deadlydog

[CmdletBinding()]
Param
(

)

Process
{

}

deadlydog

public static T InvokeMethodWithRetries<T>(Func<T> method, int maxNumberOfAttempts = 5)
{
	int numberOfAttempts = 0;
	while (numberOfAttempts < maxNumberOfAttempts)
	{ 
		try
		{
			return method.Invoke();
		}
		catch (Exception ex)

deadlydog

Get-Something dslkfjds lkjfdsl jflkdsfljdsalkf dslkf jlkdsjf lkdsj fljds lkf jdsalkf dslkfj dslfj lkdsjf ldskj flkds jflkjds lkf jdslfk jdsalkf jds jflkds jflkdsjflkds flkjdsflk jdslkf lkdsjflkdsj fljds lkf jdslfj sldjf kds flk jdsfl dsf dsljf ds jfhds lf jdsjf dsljflkds jfsjldsj fl jdsflkjdsflkjds dsfadsf dd

deadlydog

:: This script will migrate all of the IIS Applications and Configuration from the local server to the destination server.
:: This script needs to be ran from the source server that has the IIS configuration that you want to migrate.
:: MsDeploy will often generate a lot of output, so it's best to remote desktop onto the server that you want to migrate,
:: rather than running this command via PowerShell Remoting, as it will take a very long time to pipe the output back to
:: your local machine.

:: The server you are syncing to must also have Web Deploy installed on it. You can download it from:
::	http://www.microsoft.com/en-ca/download/details.aspx?id=43717
:: Be sure to do the "Complete" installation, not just the "Typical" so that the Web Deployment Agent Service gets installed.

deadlydog

function Invoke-ScriptBlockWithRetries
{
	param
	(
		[Parameter(Mandatory = $true, HelpMessage = 'The script block to execute.')]
		[ValidateNotNullOrEmpty()]
		[scriptblock] $ScriptBlock,

		[Parameter(Mandatory = $false, HelpMessage = 'The maximum number of times to retry the script block.')]
		[int] $MaxNumberOfRetries = 5,

deadlydog

using Caching;
using Microsoft.Extensions.Logging;

namespace App;

public class ExampleUsage
{
	private readonly ILogger<ExampleUsage> _logger;
	private readonly StaleMemoryCache _staleMemoryCache;
	private readonly IAuthService _authService;

deadlydog

# This code shows how to easily test a Slack webhook from PowerShell. The URL here is a dummy URL.
$slackUri = "https://hooks.slack.com/services/T025sdfsdfsdf/B67sdfsdfsdf/khAfsdfsfsfsdfsdfsdf"
$body = ConvertTo-Json @{
	pretext = "Testing Slack integration"
	text = "This is just a test to ensure the Slack webhook works and sends messages to the correct Slack channel."
	color = "#142954"
}

Invoke-RestMethod -Uri $slackUri -Method Post -Body $body -ContentType 'application/json'