dbeattie71

#!/bin/sh
# add a simple 'nuget' command to Mac OS X under Mono
# get NuGet.exe binary from http://nuget.codeplex.com/releases/view/58939
# get Microsoft.Build.dll from a Windows .NET 4.0 installation
# copy to /usr/local/bin and Robert is your father's brother....
#
PATH=/usr/local/bin:$PATH
mono --runtime=v4.0 /usr/local/bin/NuGet.exe $*

dbeattie71

#!/bin/bash
#
# git-mv-with-history -- move/rename file or folder, with history.
#
# Moving a file in git doesn't track history, so the purpose of this
# utility is best explained from the kernel wiki:
#
#   Git has a rename command git mv, but that is just for convenience.
#   The effect is indistinguishable from removing the file and adding another
#   with different name and the same content.

dbeattie71

#  ---------------------------------------------------------------------------
#
#  Description:  This file holds all my BASH configurations and aliases
#
#  Sections:
#  1.   Environment Configuration
#  2.   Make Terminal Better (remapping defaults and adding functionality)
#  3.   File and Folder Management
#  4.   Searching
#  5.   Process Management

dbeattie71

#!/usr/sh -e

#clone our private github repo with Xamarin project
git clone git@github.com/our_xamarin_project.git
cd our_xamarin_project
#update homebrew 
brew update
#install Xamarin.Studio, Xamarin.iOS, Xamarin.Android, Mono
brew cask install xamarin-mdk xamarin-ios xamarin-studio xamarin-android
#install nuget dependencies

dbeattie71

# Source Path Variables
source ~/.bash_profile

# uncomment to run this script in your local environment (outside of jenkins)
set -x
#WORKSPACE="/Users/parivedadeveloper/Projects/pariveda-finternship-2013"

# ANDROID
ANDROID_FOLDER="${WORKSPACE}/source/BBP.Droid"
ANDROID_CSPROJ="${ANDROID_FOLDER}/BBP.Droid.csproj"

dbeattie71

##Install Xcode command line tools

Xcode>Preferences>Downloads

Enable root if not already enabled: http://support.apple.com/kb/PH11331?viewlocale=en_US

##Apache

Apache is already installed, just not running.

dbeattie71

Unless specified otherwise, all of the below tinting applies to both Lollipop and pre-Lollipop using AppCompat v21. To use the support version of these attributes, remove the android namespace.  For instance, "android:colorControlNormal" becomes "colorControlNormal".  These attributes will be propagated to their corresponding attributes within the android namespace for devices running Lollipop.  Any exceptions to this will be noted by including the "android:" prefix.

All Clickable Views:
-----------
* ripple effect (Lollipop only) -- "colorControlHighlight"

Status Bar:
------------
* background (Lollipop only) - "colorPrimaryDark"

dbeattie71

Test collections are the test grouping mechanism in xUnit.net v2. They serve two purposes:

1. They delineate the "parallelism" boundary; that is, tests in the same collection will not be run in parallel against each other;
2. They offer collection-wide fixtures through the use of ICollectionFixture<TFixtureType>.

The simplest way to use test collections is simply by name. Put two classes into the same named collection, and they can derive benefit #1 above:

[Collection("MyCollection")]
public class TestClass1

dbeattie71

Param(
  [string]$projectPath=$(throw "projectPath is required (full path to .csproj file)"),
  [string]$packageName=$(throw "packageName is required"),
  [string]$configurationDirName=$(throw "configurationDirName is required"),
  [string]$keyAlias=$(throw "keyAlias is required (keystore key alias)")
)
# Parameters are defined at first line of powershell script.
# Thanks to http://docs.xamarin.com/guides/android/deployment%2C_testing%2C_and_metrics/publishing_an_application/part_1_-_preparing_an_application_for_release for this script

# Parameters :

dbeattie71

Recommendation: use the Xamarin.Android.Support.* components instead of the Mono.Android.Support.* libraries

As discussed on [1], the Xamarin.Android.Support.* components are now recommended over the Mono.Android.Support.* libraries. One reason for this is that the Xamarin.Android.Support components can be updated more frequently to keep pace with new releases from Google. Eventually, the Mono.Android.Support will be removed from Xamarin.Android. All new code should use the Xamarin.Android.Support libraries.

[1] https://bugzilla.xamarin.com/show_bug.cgi?id=15205


## Xamarin.Android.Support components in binding projects

At the moment, there's a limitation with using Xamarin.Android.Support components in Xamarin.Android Java binding projects. Specifically, the bindings projects do not yet "know" how to automatically reference the `.jar` files used by the components. This leads to error messages like: