jbachelor

# Aliases
alias cdt='cd /Users/Shared/src/TubeBuddy'
alias cds='cd /Users/Shared/src'
alias la='ls -la'
alias gs='git status'
alias gp='git pull'
alias gf='git fetch'
alias bb='cd ../..'
alias gc='git checkout'
alias ..='cd ..'

jbachelor

[Test]
public void BuildAHugeString()
{
    // arrange
    var repeatedString = "**** Hello there! I am log statement number";
    var loops = 20000;
    var stringBuilderFixedCapacity = 200000;
    int lastLogNumber = -1;
    var hugeStringBuilder = new StringBuilder(stringBuilderFixedCapacity, stringBuilderFixedCapacity);
    bool testLengthExceededFixedCapacity = false;

jbachelor

using System;
using Akavache;
using System.Collections.Generic;
using System.Diagnostics;
using System.Linq;
using System.Reactive.Linq;
using System.Threading.Tasks;

namespace MyCoolApp.Services
{

jbachelor

sudo rm -rf "/Applications/Visual Studio.app"

rm -rf ~/Library/Caches/VisualStudio
rm -rf ~/Library/Preferences/VisualStudio
rm -rf ~/Library/Preferences/Visual\ Studio
rm -rf ~/Library/Logs/VisualStudio
rm -rf ~/Library/VisualStudio
rm -rf ~/Library/Preferences/Xamarin/
rm -rf ~/Library/Application\ Support/VisualStudio
rm -rf ~/Library/Application\ Support/VisualStudio/7.0/LocalInstall/Addins/

jbachelor

Should Xamarin.Android/Resources/Resource.designer.cs be in source control?

All I have to do is open up a Xamarin.Forms solution file and build, and I typically see a huge number of changes to the Xamarin.Android/Resources/Resource.designer.cs file. The same occurs for other developers on my team. If we are each working on a feature branch of our own, this can easily lead to merge conflicts in this Resources/Resource.designer.cs file. As an auto-generated file, should this file even be in source control?

Here are the data points I've gathered so far:

• An ancient Bugzilla report from 2011 where a user suggests keeping Resources.Resource.designer.cs out of source control... But the bug was closed without any action.
  • Note that the last response (in 2012) mentions that developers can add this to their .gitignore file if they like. Does this indicate there would be no problem in doing so? It sounds like it.
• I found a [more

jbachelor

#! /bin/bash

# PREREQUISITES:
#   - You've already built the iOS app using a build configuration called "Debug":
#       - https://docs.microsoft.com/en-us/xamarin/ios/deploy-test/app-distribution/ipa-support?tabs=macos
#   - You have the libimobiledevice tool installed:
#       - https://github.com/libimobiledevice/libimobiledevice
#       - https://formulae.brew.sh/formula/ideviceinstaller
#       - https://libimobiledevice.org/

jbachelor

[Test]
public async Task TaskDotRunTestAsync()
{
    var timer = new Stopwatch();
    Console.WriteLine($"**** {this.GetType().Name}.{nameof(TaskDotRunTestAsync)}: Beginning test ({timer.ElapsedMilliseconds}ms)");
    timer.Start();
    try
    {
        Console.WriteLine($"**** {this.GetType().Name}.{nameof(TaskDotRunTestAsync)}: About to start Task.Run ({timer.ElapsedMilliseconds}ms)");
        // Run this test twice... Once with the await on the following line, once without.

jbachelor

namespace MyCoolMobileApp.Services.DependencyServices
{
    public interface ISettingsAppLauncher
    {
        void LaunchSettingsApp(string appBundleId);
    }
}

jbachelor

bool didOpenUri = await Xamarin.Essentials.Launcher.TryOpenAsync("?????????????????");